{"thread":{"id":"28764","subject":"pull is not a git command - 1.7.6.4","startedAt":"2011-10-25T15:58:06Z","lastAt":"2011-10-25T18:10:33Z","messageCount":7,"participants":["Eugene Sajine","Matthieu Moy","Junio C Hamano"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"178274","messageId":"CAPZPVFbakHo0hgz3bo+SLMuYnQSEA=ab+4W92+Lr5Fq4XZy2PA@mail.gmail.com","threadId":"28764","inReplyTo":null,"subject":"pull is not a git command - 1.7.6.4","fromName":"Eugene Sajine","fromEmail":"euguess@gmail.com","sentAt":"2011-10-25T15:58:06Z","receivedAt":"2011-10-25T15:58:06Z","isPatch":false,"sender":{"key":"euguess@gmail.com","avatar":null},"body":"Hi,\n\n\nWe have built git 1.7.6.4 and we have a following problem with it:\n\nIt is localted in a folder /usr/local/git-1.7.6.4/\nIf the user has both /usr/local/git-1.7.6.4/ and\n/usr/local/git-1.7.6.4/bin in $PATH variable then git works fine.\nIf the user doesn't have the upper level folder in the $PATH then git\ncannot execute some commands like \"git pull\".\nIt says pull is not a git command. Or git gc complains that repack is\nnot a git command.\n\nIt doesn't seem to be the case with 1.7.4.1\n\nWas there any change between those versions that i missed, or may be\nthere is some property we have to specify during build?\n\nThanks,\nEugene\n"},{"id":"178278","messageId":"vpqpqhlox45.fsf@bauges.imag.fr","threadId":"28764","inReplyTo":"CAPZPVFbakHo0hgz3bo+SLMuYnQSEA=ab+4W92+Lr5Fq4XZy2PA@mail.gmail.com","subject":"Re: pull is not a git command - 1.7.6.4","fromName":"Matthieu Moy","fromEmail":"matthieu.moy@grenoble-inp.fr","sentAt":"2011-10-25T16:27:06Z","receivedAt":"2011-10-25T16:27:06Z","isPatch":false,"sender":{"key":"matthieu.moy@grenoble-inp.fr","avatar":"https://gravatar.com/avatar/72c8a2705971a25dfaff23cece15130d405685845d911aedd5667ace277f3fc5?d=mp&s=160"},"body":"Eugene Sajine writes:\n\n> Hi,\n>\n>\n> We have built git 1.7.6.4 and we have a following problem with it:\n\nWhich command did you use to compile it? What does\n\n git --exec-path\n\nsay?\n\n-- \nMatthieu Moy\nhttp://www-verimag.imag.fr/~moy/\n"},{"id":"178280","messageId":"7vipnd3trk.fsf@alter.siamese.dyndns.org","threadId":"28764","inReplyTo":"CAPZPVFbakHo0hgz3bo+SLMuYnQSEA=ab+4W92+Lr5Fq4XZy2PA@mail.gmail.com","subject":"Re: pull is not a git command - 1.7.6.4","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2011-10-25T16:45:03Z","receivedAt":"2011-10-25T16:45:03Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Eugene Sajine writes:\n\n> We have built git 1.7.6.4 and we have a following problem with it:\n> .,,\n> It doesn't seem to be the case with 1.7.4.1\n>\n> Was there any change between those versions that i missed, or may be\n> there is some property we have to specify during build?\n\nNothing I can think of offhand that you need to specify _differently_\nbetween the build procedures of these two versions.\n\nJust a wild guess. perhaps you specified prefix=/usr/local/git-1.7.4.1/\neons ago when you built and installed 1.7.4.1 like this:\n\n make prefix=/usr/local/git-1.7.4.1 all install\n\nand then you did it differently when you installed 1.7.6.4, e.g.\n\n make all\n make prefix=/usr/local/git-1.7.6.4 install\n"},{"id":"178281","messageId":"CAPZPVFZCQdOsAUMdbcZjmGxVgX5LuKKwcob=qBuNmyX7kYwA4A@mail.gmail.com","threadId":"28764","inReplyTo":"vpqpqhlox45.fsf@bauges.imag.fr","subject":"Re: pull is not a git command - 1.7.6.4","fromName":"Eugene Sajine","fromEmail":"euguess@gmail.com","sentAt":"2011-10-25T16:50:48Z","receivedAt":"2011-10-25T16:50:48Z","isPatch":false,"sender":{"key":"euguess@gmail.com","avatar":null},"body":"On Tue, Oct 25, 2011 at 12:27 PM, Matthieu Moy\n wrote:\n> Eugene Sajine writes:\n>\n>> Hi,\n>>\n>>\n>> We have built git 1.7.6.4 and we have a following problem with it:\n>\n> Which command did you use to compile it? What does\n>\n>  git --exec-path\n>\n> say?\n>\n> --\n> Matthieu Moy\n> http://www-verimag.imag.fr/~moy/\n>\n\nI was not building it myself so i cannot say what command exactly was\nused, but i will check it.\nOTOH git --exec-path shows:\nfor version 1.7.4.1 that works properly -\n/usr/local/git-1.7.4.1/libexec/git-core\nFor version 1.7.6.4 libexec is located in some other folder...\n\nLet me check what is this all about.\n\nThanks,\nEugene\n"},{"id":"178282","messageId":"CAPZPVFanWTpCDO+A0dV4TWUVx-22VjFOdk6f7cmgfU59GqG3sQ@mail.gmail.com","threadId":"28764","inReplyTo":"7vipnd3trk.fsf@alter.siamese.dyndns.org","subject":"Re: pull is not a git command - 1.7.6.4","fromName":"Eugene Sajine","fromEmail":"euguess@gmail.com","sentAt":"2011-10-25T16:52:14Z","receivedAt":"2011-10-25T16:52:14Z","isPatch":false,"sender":{"key":"euguess@gmail.com","avatar":null},"body":"On Tue, Oct 25, 2011 at 12:45 PM, Junio C Hamano wrote:\n> Eugene Sajine writes:\n>\n>> We have built git 1.7.6.4 and we have a following problem with it:\n>> .,,\n>> It doesn't seem to be the case with 1.7.4.1\n>>\n>> Was there any change between those versions that i missed, or may be\n>> there is some property we have to specify during build?\n>\n> Nothing I can think of offhand that you need to specify _differently_\n> between the build procedures of these two versions.\n>\n> Just a wild guess. perhaps you specified prefix=/usr/local/git-1.7.4.1/\n> eons ago when you built and installed 1.7.4.1 like this:\n>\n>    make prefix=/usr/local/git-1.7.4.1 all install\n>\n> and then you did it differently when you installed 1.7.6.4, e.g.\n>\n>    make all\n>    make prefix=/usr/local/git-1.7.6.4 install\n>\n>\n\n\nAre you saying that the first command is more correct?\nI will check it.\n\nThanks a lot,\nEugene\n"},{"id":"178284","messageId":"vpqr521j98h.fsf@bauges.imag.fr","threadId":"28764","inReplyTo":"CAPZPVFanWTpCDO+A0dV4TWUVx-22VjFOdk6f7cmgfU59GqG3sQ@mail.gmail.com","subject":"Re: pull is not a git command - 1.7.6.4","fromName":"Matthieu Moy","fromEmail":"matthieu.moy@grenoble-inp.fr","sentAt":"2011-10-25T17:01:50Z","receivedAt":"2011-10-25T17:01:50Z","isPatch":false,"sender":{"key":"matthieu.moy@grenoble-inp.fr","avatar":"https://gravatar.com/avatar/72c8a2705971a25dfaff23cece15130d405685845d911aedd5667ace277f3fc5?d=mp&s=160"},"body":"Eugene Sajine writes:\n\n> On Tue, Oct 25, 2011 at 12:45 PM, Junio C Hamano wrote:\n>\n>> Just a wild guess. perhaps you specified prefix=/usr/local/git-1.7.4.1/\n>> eons ago when you built and installed 1.7.4.1 like this:\n>>\n>>    make prefix=/usr/local/git-1.7.4.1 all install\n>>\n>> and then you did it differently when you installed 1.7.6.4, e.g.\n>>\n>>    make all\n>>    make prefix=/usr/local/git-1.7.6.4 install\n>>\n>>\n>\n>\n> Are you saying that the first command is more correct?\n> I will check it.\n\nAt build time, Git registers the \"exec path\" (i.e. where to find\ngit- executables). So, if you run \"make all\" without specifying\nthe install path, Git will set an arbitrary exec-path, and the\ninstallation won't work.\n\n-- \nMatthieu Moy\nhttp://www-verimag.imag.fr/~moy/\n"},{"id":"178289","messageId":"CAPZPVFZKNdDcnaVn237gArqdBuc4ek77vxsp8BMaicARBTKqBg@mail.gmail.com","threadId":"28764","inReplyTo":"vpqr521j98h.fsf@bauges.imag.fr","subject":"Re: pull is not a git command - 1.7.6.4","fromName":"Eugene Sajine","fromEmail":"euguess@gmail.com","sentAt":"2011-10-25T18:10:33Z","receivedAt":"2011-10-25T18:10:33Z","isPatch":false,"sender":{"key":"euguess@gmail.com","avatar":null},"body":"On Tue, Oct 25, 2011 at 1:01 PM, Matthieu Moy\n wrote:\n> Eugene Sajine writes:\n>\n>> On Tue, Oct 25, 2011 at 12:45 PM, Junio C Hamano wrote:\n>>\n>>> Just a wild guess. perhaps you specified prefix=/usr/local/git-1.7.4.1/\n>>> eons ago when you built and installed 1.7.4.1 like this:\n>>>\n>>>    make prefix=/usr/local/git-1.7.4.1 all install\n>>>\n>>> and then you did it differently when you installed 1.7.6.4, e.g.\n>>>\n>>>    make all\n>>>    make prefix=/usr/local/git-1.7.6.4 install\n>>>\n>>>\n>>\n>>\n>> Are you saying that the first command is more correct?\n>> I will check it.\n>\n> At build time, Git registers the \"exec path\" (i.e. where to find\n> git- executables). So, if you run \"make all\" without specifying\n> the install path, Git will set an arbitrary exec-path, and the\n> installation won't work.\n>\n> --\n> Matthieu Moy\n> http://www-verimag.imag.fr/~moy/\n>\n\nMatthieu/Junio,\n\nThank you very much for your help - there was a mistake made during\nthe build where the exec path folder was incorrect and unreachable.\n\nThanks!\n"}]}