{"thread":{"id":"19780","subject":"[bug] git cannot find \"git pull\"?","startedAt":"2009-06-12T00:10:09Z","lastAt":"2009-06-15T17:23:13Z","messageCount":14,"participants":["Jeff Garzik","Todd Zullinger","Junio C Hamano","J.H."],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"116112","messageId":"4A319CE1.6040201@garzik.org","threadId":"19780","inReplyTo":null,"subject":"[bug] git cannot find \"git pull\"?","fromName":"Jeff Garzik","fromEmail":"jeff@garzik.org","sentAt":"2009-06-12T00:10:09Z","receivedAt":"2009-06-12T00:10:09Z","isPatch":false,"sender":{"key":"jeff@garzik.org","avatar":null},"body":"\nI just upgraded to Fedora 11 (git-1.6.2.2-1.fc11.x86_64), and see the \nfollowing:\n\n> [jgarzik@viper linux-2.6]$ git pull\n> git: 'pull' is not a git-command. See 'git --help'.\n> \n> Did you mean this?\n> \tshell\n\n\nBleh...  :)  \"git --help\" indicates that \"git pull\" still exists.\n\n\tJeff\n"},{"id":"116113","messageId":"20090612011737.GB5076@inocybe.localdomain","threadId":"19780","inReplyTo":"4A319CE1.6040201@garzik.org","subject":"Re: [bug] git cannot find \"git pull\"?","fromName":"Todd Zullinger","fromEmail":"tmz@pobox.com","sentAt":"2009-06-12T01:17:38Z","receivedAt":"2009-06-12T01:17:38Z","isPatch":false,"sender":{"key":"tmz@pobox.com","avatar":"https://avatars.githubusercontent.com/u/806319?v=4"},"body":"Hi Jeff,\n\nJeff Garzik wrote:\n> I just upgraded to Fedora 11 (git-1.6.2.2-1.fc11.x86_64), and see\n> the following:\n>\n>> [jgarzik@viper linux-2.6]$ git pull\n>> git: 'pull' is not a git-command. See 'git --help'.\n>>\n>> Did you mean this?\n>> \tshell\n>\n>\n> Bleh...  :)  \"git --help\" indicates that \"git pull\" still exists.\n\nYuck.  I can't reproduce this (and I would hope that if the Fedora\npackages have been broken for many weeks that someone would have\nnoticed and complained loudly before the release...).  Of course, if\nthere is something horribly wrong with the Fedora packages, I'll try\nto get it fixed as quickly as possible.\n\nDo you happen to have any strange PATH set, other non-packaged git\nbinaries installed, or funky aliases/settings in your git config?\nDoes the problem occur after an upgrade or clean install?  For all\nusers?\n\nIt is notable that Fedora 11 is the first Fedora release that follows\nthe git 1.6.x defaults and installs most git binaries outside of PATH.\nI don't think that would cause this, and I haven't had any troubles\nrunning these packages for many months, but that's never stopped\nreally obvious bugs in the past...\n\n(Apologies for the obscenely silly questions.  I'm just hoping they\nmight help lead to the root cause so we can make sure it's fixed. ;)\n\n-- \nTodd        OpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp\n~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\nIf the triangles were to make a God they would give him three sides.\n    -- Montesquieu\n\n"},{"id":"116114","messageId":"7v7hzidvcj.fsf@alter.siamese.dyndns.org","threadId":"19780","inReplyTo":"20090612011737.GB5076@inocybe.localdomain","subject":"Re: [bug] git cannot find \"git pull\"?","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2009-06-12T02:44:28Z","receivedAt":"2009-06-12T02:44:28Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Todd Zullinger <tmz@pobox.com> writes:\n\n> It is notable that Fedora 11 is the first Fedora release that follows\n> the git 1.6.x defaults and installs most git binaries outside of PATH.\n> I don't think that would cause this, and I haven't had any troubles\n> running these packages for many months, but that's never stopped\n> really obvious bugs in the past...\n\nI do not follow distro packaged versions of git, but it may help to double\ncheck your spec changes against the output of\n\n    $ git log -p v1.5.6..v1.6.2.2 -- git.spec.in\n\nto see which paths need to be updated.\n\nOf course, you might not be using a specfile remotely similar to what we\nhave in-tree (I believe it was originally done by Chris Wright who is\nlisted as one of the persons who have something to do with Fedora packaged\nversions of git in your maintainers list), so this may not be a helpful\ntip at all, in which case I apologize...\n"},{"id":"116117","messageId":"20090612031853.GC5076@inocybe.localdomain","threadId":"19780","inReplyTo":"7v7hzidvcj.fsf@alter.siamese.dyndns.org","subject":"Re: [bug] git cannot find \"git pull\"?","fromName":"Todd Zullinger","fromEmail":"tmz@pobox.com","sentAt":"2009-06-12T03:18:53Z","receivedAt":"2009-06-12T03:18:53Z","isPatch":false,"sender":{"key":"tmz@pobox.com","avatar":"https://avatars.githubusercontent.com/u/806319?v=4"},"body":"Junio C Hamano wrote:\n> Todd Zullinger <tmz@pobox.com> writes:\n>\n>> It is notable that Fedora 11 is the first Fedora release that\n>> follows the git 1.6.x defaults and installs most git binaries\n>> outside of PATH.  I don't think that would cause this, and I\n>> haven't had any troubles running these packages for many months,\n>> but that's never stopped really obvious bugs in the past...\n>\n> I do not follow distro packaged versions of git, but it may help to\n> double check your spec changes against the output of\n>\n>     $ git log -p v1.5.6..v1.6.2.2 -- git.spec.in\n>\n> to see which paths need to be updated.\n\nAFAIK, we're installing things in the correct locations.  git-pull is\nlocated with the rest of the git commands in /usr/libexec/git-core\n(which is what 'git --exec-path' shows).\n\nThe Fedora 10 packages (unfortunately, IMO) set gitexecdir=%{_bindir},\nbut that was rectified as soon as the Fedora 11 cycle started and we\ntried to track each upstream git release closely until things were\nfrozen to make the release.  I know there are a good number of fedora\ndevelopers and packagers who use git, so I would really expect that\nwe'd have seen pitchfork wielding mobs if we broke the packaging\nbadly. ;)\n\n> Of course, you might not be using a specfile remotely similar to\n> what we have in-tree (I believe it was originally done by Chris\n> Wright who is listed as one of the persons who have something to do\n> with Fedora packaged versions of git in your maintainers list), so\n> this may not be a helpful tip at all, in which case I apologize...\n\nYour help and insight is always welcome Junio. :)\n\nChris has been busy with other things for a while.  I started helping\nwith git package maintenance only in the last 6 months or so.  Over\ntime, the spec file we have has drifted a bit from what is in git.git,\nthough not terribly so.  I need to spend some time and look at what,\nif any, changes in the Fedora spec file would be good candidates for\nsubmitting to git.git.  I have been primarily concerned with making\nthings work cleanly on Fedora and RHEL/CentOS though, so some of the\nchanges may not be as generic as they ought to be if they are to be\nincluded in git.git.\n\n-- \nTodd        OpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp\n~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\nRowe's Rule: The odds are five to six that the light at the end of the\ntunnel is the headlight of an oncoming train.\n    -- Paul Dickson\n\n"},{"id":"116121","messageId":"7viqj2c9rs.fsf@alter.siamese.dyndns.org","threadId":"19780","inReplyTo":"20090612031853.GC5076@inocybe.localdomain","subject":"Re: [bug] git cannot find \"git pull\"?","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2009-06-12T05:15:51Z","receivedAt":"2009-06-12T05:15:51Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Todd Zullinger <tmz@pobox.com> writes:\n\n> Chris has been busy with other things for a while.  I started helping\n> with git package maintenance only in the last 6 months or so.  Over\n> time, the spec file we have has drifted a bit from what is in git.git,\n> though not terribly so.  I need to spend some time and look at what,\n> if any, changes in the Fedora spec file would be good candidates for\n> submitting to git.git.  I have been primarily concerned with making\n> things work cleanly on Fedora and RHEL/CentOS though, so some of the\n> changes may not be as generic as they ought to be if they are to be\n> included in git.git.\n\nI use the one in git.git only to cut the Fedora 9 packages for consumption\nby k.org people.  I do not know what their upgrade plans are, but last\ntime they upgraded from FC 5 to Fedora 9 I had to scramble around and find\nan i386 box to produce binaries (the machine available to me at k.org is\namd64).  Perhaps I should start preparing Fedora 11 environment now it is\nfinally released, but before that I need to procure a new development box\nto host it in a vm, as the current box that is the primary integration\nmachine for git and that hosts the Fedora 9 i386 vm has got too tight and\nI've been limping along; it does not have enough room to host another vm\n(and it is not even hardware vm capable)...\n"},{"id":"116124","messageId":"4A31FB22.7030500@eaglescrag.net","threadId":"19780","inReplyTo":"7viqj2c9rs.fsf@alter.siamese.dyndns.org","subject":"Re: [bug] git cannot find \"git pull\"?","fromName":"J.H.","fromEmail":"warthog19@eaglescrag.net","sentAt":"2009-06-12T06:52:18Z","receivedAt":"2009-06-12T06:52:18Z","isPatch":false,"sender":{"key":"warthog19@eaglescrag.net","avatar":null},"body":"Junio C Hamano wrote:\n> Todd Zullinger <tmz@pobox.com> writes:\n> \n>> Chris has been busy with other things for a while.  I started helping\n>> with git package maintenance only in the last 6 months or so.  Over\n>> time, the spec file we have has drifted a bit from what is in git.git,\n>> though not terribly so.  I need to spend some time and look at what,\n>> if any, changes in the Fedora spec file would be good candidates for\n>> submitting to git.git.  I have been primarily concerned with making\n>> things work cleanly on Fedora and RHEL/CentOS though, so some of the\n>> changes may not be as generic as they ought to be if they are to be\n>> included in git.git.\n> \n> I use the one in git.git only to cut the Fedora 9 packages for consumption\n> by k.org people.  I do not know what their upgrade plans are, but last\n> time they upgraded from FC 5 to Fedora 9 I had to scramble around and find\n> an i386 box to produce binaries (the machine available to me at k.org is\n> amd64).  Perhaps I should start preparing Fedora 11 environment now it is\n> finally released, but before that I need to procure a new development box\n> to host it in a vm, as the current box that is the primary integration\n> machine for git and that hosts the Fedora 9 i386 vm has got too tight and\n> I've been limping along; it does not have enough room to host another vm\n> (and it is not even hardware vm capable)...\n\nThe general idea is when we aren't getting security updates for our \ncurrent install base, that is when we (k.org) will make the move to upgrade.\n\nThat said, since 11 just came out I'm going to have to start considering \nand working on an upgrade plan, but I wouldn't expect that to be getting \nto a point where it would affect you for a few months yet, and I would \nhate to upgrade to Fedora 11 before it's had a chance to settle and stew.\n\n- John 'Warthog9' Hawley\n"},{"id":"116140","messageId":"4A323C56.1090703@garzik.org","threadId":"19780","inReplyTo":"20090612011737.GB5076@inocybe.localdomain","subject":"Re: [bug] git cannot find \"git pull\"?","fromName":"Jeff Garzik","fromEmail":"jeff@garzik.org","sentAt":"2009-06-12T11:30:30Z","receivedAt":"2009-06-12T11:30:30Z","isPatch":false,"sender":{"key":"jeff@garzik.org","avatar":null},"body":"Todd Zullinger wrote:\n> Hi Jeff,\n> \n> Jeff Garzik wrote:\n>> I just upgraded to Fedora 11 (git-1.6.2.2-1.fc11.x86_64), and see\n>> the following:\n>>\n>>> [jgarzik@viper linux-2.6]$ git pull\n>>> git: 'pull' is not a git-command. See 'git --help'.\n>>>\n>>> Did you mean this?\n>>> \tshell\n>>\n>> Bleh...  :)  \"git --help\" indicates that \"git pull\" still exists.\n> \n> Yuck.  I can't reproduce this (and I would hope that if the Fedora\n> packages have been broken for many weeks that someone would have\n> noticed and complained loudly before the release...).  Of course, if\n> there is something horribly wrong with the Fedora packages, I'll try\n> to get it fixed as quickly as possible.\n> \n> Do you happen to have any strange PATH set, other non-packaged git\n> binaries installed, or funky aliases/settings in your git config?\n> Does the problem occur after an upgrade or clean install?  For all\n> users?\n\nNo strange PATH settings, and this was a completely fresh \nFedora-11/x86-64 reformat and reinstall...\n\nAdding \"--exec-path=/usr/libexec/git-core\" seems to work.\n\nI wonder if it is looking for /usr/libexec64/git-core or something?\n\n\tJeff\n"},{"id":"116173","messageId":"4A32A814.5050802@garzik.org","threadId":"19780","inReplyTo":"4A323C56.1090703@garzik.org","subject":"Re: [bug] git cannot find \"git pull\"?","fromName":"Jeff Garzik","fromEmail":"jeff@garzik.org","sentAt":"2009-06-12T19:10:12Z","receivedAt":"2009-06-12T19:10:12Z","isPatch":false,"sender":{"key":"jeff@garzik.org","avatar":null},"body":"Jeff Garzik wrote:\n> No strange PATH settings, and this was a completely fresh \n> Fedora-11/x86-64 reformat and reinstall...\n> \n> Adding \"--exec-path=/usr/libexec/git-core\" seems to work.\n> \n> I wonder if it is looking for /usr/libexec64/git-core or something?\n\nSame failure (with same workaround) on Fedora 11/i386, fresh install.\n\n\tJeff\n"},{"id":"116179","messageId":"20090612202642.GI5076@inocybe.localdomain","threadId":"19780","inReplyTo":"4A32A814.5050802@garzik.org","subject":"Re: [bug] git cannot find \"git pull\"?","fromName":"Todd Zullinger","fromEmail":"tmz@pobox.com","sentAt":"2009-06-12T20:26:42Z","receivedAt":"2009-06-12T20:26:42Z","isPatch":false,"sender":{"key":"tmz@pobox.com","avatar":"https://avatars.githubusercontent.com/u/806319?v=4"},"body":"Jeff Garzik wrote:\n> Jeff Garzik wrote:\n>> No strange PATH settings, and this was a completely fresh\n>> Fedora-11/x86-64 reformat and reinstall...\n>>\n>> Adding \"--exec-path=/usr/libexec/git-core\" seems to work.\n>>\n>> I wonder if it is looking for /usr/libexec64/git-core or something?\n>\n> Same failure (with same workaround) on Fedora 11/i386, fresh\n> install.\n\nWell hell.  I can't reproduce this.  I setup an F-11/x86_64 instance\nand had no troubles.  Similarly for i386 using the Live USB image.\n\nIs it possible that some other package is screwing up the git search\npath?  Running strings on /usr/bin/git I find libexec/git-core, so I\ndon't think it's trying libexec64, which doesn't exist in an Fedora\nrelease that I know of.\n\nI'd be very curious if anyone else can reproduce this and what\ndifferences there are in the package list between my working system\nand your broken ones.\n\n-- \nTodd        OpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp\n~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\nEducation is a state-controlled manufactory of echoes.\n    -- Norman Douglas\n\n"},{"id":"116180","messageId":"4A32BF52.50603@garzik.org","threadId":"19780","inReplyTo":"20090612202642.GI5076@inocybe.localdomain","subject":"Re: [bug] git cannot find \"git pull\"?","fromName":"Jeff Garzik","fromEmail":"jeff@garzik.org","sentAt":"2009-06-12T20:49:22Z","receivedAt":"2009-06-12T20:49:22Z","isPatch":false,"sender":{"key":"jeff@garzik.org","avatar":null},"body":"Todd Zullinger wrote:\n> Jeff Garzik wrote:\n>> Jeff Garzik wrote:\n>>> No strange PATH settings, and this was a completely fresh\n>>> Fedora-11/x86-64 reformat and reinstall...\n>>>\n>>> Adding \"--exec-path=/usr/libexec/git-core\" seems to work.\n>>>\n>>> I wonder if it is looking for /usr/libexec64/git-core or something?\n>> Same failure (with same workaround) on Fedora 11/i386, fresh\n>> install.\n> \n> Well hell.  I can't reproduce this.  I setup an F-11/x86_64 instance\n> and had no troubles.  Similarly for i386 using the Live USB image.\n> \n> Is it possible that some other package is screwing up the git search\n> path?  Running strings on /usr/bin/git I find libexec/git-core, so I\n> don't think it's trying libexec64, which doesn't exist in an Fedora\n> release that I know of.\n> \n> I'd be very curious if anyone else can reproduce this and what\n> differences there are in the package list between my working system\n> and your broken ones.\n\nFWIW, to reproduce my Fedora install, this is the setup I always use for \nmy lab computers:\n\n* perform a fresh format + install, not an upgrade\n* uncheck 'office' category\n* check 'software development' category\n* do not select 'customize now', thus using Fedora's default package \nselection\n\nSo it is 100% Fedora-shipped software in $PATH...\n\nRegards,\n\n\tJeff\n"},{"id":"116232","messageId":"20090613150451.GK5076@inocybe.localdomain","threadId":"19780","inReplyTo":"4A32BF52.50603@garzik.org","subject":"Re: [bug] git cannot find \"git pull\"?","fromName":"Todd Zullinger","fromEmail":"tmz@pobox.com","sentAt":"2009-06-13T15:04:51Z","receivedAt":"2009-06-13T15:04:51Z","isPatch":false,"sender":{"key":"tmz@pobox.com","avatar":"https://avatars.githubusercontent.com/u/806319?v=4"},"body":"Jeff Garzik wrote:\n> FWIW, to reproduce my Fedora install, this is the setup I always use\n> for my lab computers:\n>\n> * perform a fresh format + install, not an upgrade\n> * uncheck 'office' category\n> * check 'software development' category\n> * do not select 'customize now', thus using Fedora's default package\n> selection\n\nStranger and stranger.  I followed the above steps with an F-11/x86\nnetwork install and then ran:\n\n    $ git clone git://repo.or.cz/git.git\n    ...\n    $ cd git ; git pull\n    Already up-to-date.\n\n    $ rpm -q git\n    git-1.6.2.2-1.fc11.i586\n\n    $ rpm -ql git | grep git-pull$\n    /usr/libexec/git-core/git-pull\n\nDoes git --exec-path report something other than /usr/libexec/git-core\non your installs?  Is git-pull located in /usr/libexec/git-core?  Does\n'rpm -V git' return anything?\n\n-- \nTodd        OpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp\n~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\nFew things are harder to put up with than a good example.\n    -- Mark Twain (1835-1910)\n\n"},{"id":"116241","messageId":"4A33E069.4050401@garzik.org","threadId":"19780","inReplyTo":"20090613150451.GK5076@inocybe.localdomain","subject":"Re: [bug] git cannot find \"git pull\"?","fromName":"Jeff Garzik","fromEmail":"jeff@garzik.org","sentAt":"2009-06-13T17:22:49Z","receivedAt":"2009-06-13T17:22:49Z","isPatch":false,"sender":{"key":"jeff@garzik.org","avatar":null},"body":"Todd Zullinger wrote:\n> Jeff Garzik wrote:\n>> FWIW, to reproduce my Fedora install, this is the setup I always use\n>> for my lab computers:\n>>\n>> * perform a fresh format + install, not an upgrade\n>> * uncheck 'office' category\n>> * check 'software development' category\n>> * do not select 'customize now', thus using Fedora's default package\n>> selection\n> \n> Stranger and stranger.  I followed the above steps with an F-11/x86\n> network install and then ran:\n\nFound it!  A forgotten package I created, a collective of shell scripts, \nwas setting GIT_EXEC_PATH=/usr/local/bin.\n\nGiven that /usr/local/bin/*git* has not existed on my systems for a long \ntime, it appears that this is a new behavior, being a bit more strict in \ncomplaining about an invalid GIT_EXEC_PATH, rather than simply falling \nback to the internal compiled default (/usr/libexec/git-core).\n\nThings are working again now that the local GIT_EXEC_PATH export is removed.\n\n\tJeff\n"},{"id":"116242","messageId":"20090613173600.GL5076@inocybe.localdomain","threadId":"19780","inReplyTo":"4A33E069.4050401@garzik.org","subject":"Re: [bug] git cannot find \"git pull\"?","fromName":"Todd Zullinger","fromEmail":"tmz@pobox.com","sentAt":"2009-06-13T17:36:00Z","receivedAt":"2009-06-13T17:36:00Z","isPatch":false,"sender":{"key":"tmz@pobox.com","avatar":"https://avatars.githubusercontent.com/u/806319?v=4"},"body":"Jeff Garzik wrote:\n> Found it!  A forgotten package I created, a collective of shell\n> scripts, was setting GIT_EXEC_PATH=/usr/local/bin.\n\nPhew.  I was worried I might have to start drinking much earlier than\nusual today. ;)\n\n> Given that /usr/local/bin/*git* has not existed on my systems for a\n> long time, it appears that this is a new behavior, being a bit more\n> strict in complaining about an invalid GIT_EXEC_PATH, rather than\n> simply falling back to the internal compiled default\n> (/usr/libexec/git-core).\n\nWithout looking closely at the make files and build logic, is it\nperhaps something caused by the previous Fedora git-1.6.0.x packages\npassing gitexecdir=%{_bindir} to make, while the F-11 and newer\npackages do not set any gitexecdir?\n\n> Things are working again now that the local GIT_EXEC_PATH export is\n> removed.\n\nGlad you found the culprit.\n\n-- \nTodd        OpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp\n~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\nI always keep a supply of stimulant handy in case I see a snake -\nwhich I also keep handy.\n    -- W. C. Fields\n\n"},{"id":"116347","messageId":"4A368381.3040601@garzik.org","threadId":"19780","inReplyTo":"20090613173600.GL5076@inocybe.localdomain","subject":"Re: [bug] git cannot find \"git pull\"?","fromName":"Jeff Garzik","fromEmail":"jeff@garzik.org","sentAt":"2009-06-15T17:23:13Z","receivedAt":"2009-06-15T17:23:13Z","isPatch":false,"sender":{"key":"jeff@garzik.org","avatar":null},"body":"Todd Zullinger wrote:\n> Jeff Garzik wrote:\n>> Found it!  A forgotten package I created, a collective of shell\n>> scripts, was setting GIT_EXEC_PATH=/usr/local/bin.\n> \n> Phew.  I was worried I might have to start drinking much earlier than\n> usual today. ;)\n> \n>> Given that /usr/local/bin/*git* has not existed on my systems for a\n>> long time, it appears that this is a new behavior, being a bit more\n>> strict in complaining about an invalid GIT_EXEC_PATH, rather than\n>> simply falling back to the internal compiled default\n>> (/usr/libexec/git-core).\n> \n> Without looking closely at the make files and build logic, is it\n> perhaps something caused by the previous Fedora git-1.6.0.x packages\n> passing gitexecdir=%{_bindir} to make, while the F-11 and newer\n> packages do not set any gitexecdir?\n\nPerhaps, though it seems more likely that this was a change in the core \ngit code, and not related to hardcoding gitexecdir= in the RPM build \nprocess.\n\n\n\tJeff\n"}]}