{"thread":{"id":"19552","subject":"Strangely hosed git install","startedAt":"2009-05-28T07:08:58Z","lastAt":"2009-05-28T10:11:01Z","messageCount":8,"participants":["Martin Langhoff","Junio C Hamano","Michael J Gruber"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"114893","messageId":"46a038f90905280008h5510d03aj5f6e5728ca075027@mail.gmail.com","threadId":"19552","inReplyTo":null,"subject":"Strangely hosed git install","fromName":"Martin Langhoff","fromEmail":"martin.langhoff@gmail.com","sentAt":"2009-05-28T07:08:58Z","receivedAt":"2009-05-28T07:08:58Z","isPatch":false,"sender":{"key":"martin.langhoff@gmail.com","avatar":"https://gravatar.com/avatar/1e3f311b6c4c15836501901ca58f8c0b0667246488084ba524d8bc9867e22fd9?d=mp&s=160"},"body":"My main laptop (and part-time dev box) has a partially hosed git\ninstallation. This is an ubuntu intrepid machine where I have been\nbuilding git from src for a while. Perhaps there's a way to diagnose\nthis before I take more drastic measures :-)\n\nSo far gc, repack and stash show errors. No dataloss AFAICS (though\nthe git stash errors scared me initially).\n\ngc and repack error out thus:\n\n$ git gc\nusage: git-pack-objects [{ -q | --progress | --all-progress }]\n        [--max-pack-size=N] [--local] [--incremental]\n        [--window=N] [--window-memory=N] [--depth=N]\n        [--no-reuse-delta] [--no-reuse-object] [--delta-base-offset]\n        [--threads=N] [--non-empty] [--revs [--unpacked | --all]*] [--reflog]\n        [--stdout | base-name] [--keep-unreachable] [<ref-list | <object-list]\nerror: failed to run repack\n$ echo $?\n255\n\nAnd stash...\n\n$ git stash\nusage: git-diff-index [-m] [--cached] [<common diff options>]\n<tree-ish> [<path>...]\ncommon diff options:\n(...)\n\nusage: git-diff-index [-m] [--cached] [<common diff options>]\n<tree-ish> [<path>...]\ncommon diff options:\n(...)\nSaved working directory and index state \"WIP on master: 1eac877... WIP\nolpc-update-query: if the lease is due soon avoid\nrandomly_do_nothing()\"\nHEAD is now at 1eac877... WIP olpc-update-query: if the lease is due\nsoon avoid randomly_do_nothing()\n(To restore them type \"git stash apply\")\n$ echo $?\n0\n$ git stash show\n olpc-update-query |    5 +++++\n 1 files changed, 5 insertions(+), 0 deletions(-)\n$ git stash apply # does the right thing\n\nSome background diagnostics info\n\n - $ git --version\n   git version 1.6.3.1.26.gf5b223\n\n - $ which git\n   /home/martin/bin/git\n  # there is no other git install anywhere on the box\n\n - the git-core package was once installed temporarily (to try out a\npackage that depends on git-core)\n\n - some oldstyle \"dashed\" commands trigger a helper bash extension, thus\n   $ git-diff\n   The program 'git-diff' is currently not installed.  You can install\nit by typing:\n   sudo apt-get install git-core\n   bash: git-diff: command not found\n\n\nI can't figure out what is wrong with the install. I have bisected a\nfew bugs in the past, but that had never left any traces behind.\n\nIt's not a serious problem -- I just wonder whether it'd affect other\npeople developing / tracking git.\n\ncheers,\n\n\n\nm\n--\n martin.langhoff@gmail.com\n martin@laptop.org -- School Server Architect\n - ask interesting questions\n - don't get distracted with shiny stuff  - working code first\n - http://wiki.laptop.org/go/User:Martinlanghoff\n"},{"id":"114895","messageId":"7vprdthezg.fsf@alter.siamese.dyndns.org","threadId":"19552","inReplyTo":"46a038f90905280008h5510d03aj5f6e5728ca075027@mail.gmail.com","subject":"Re: Strangely hosed git install","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2009-05-28T07:18:59Z","receivedAt":"2009-05-28T07:18:59Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Martin Langhoff <martin.langhoff@gmail.com> writes:\n\n> My main laptop (and part-time dev box) has a partially hosed git\n> installation. This is an ubuntu intrepid machine where I have been\n> building git from src for a while. Perhaps there's a way to diagnose\n> this before I take more drastic measures :-)\n>\n> So far gc, repack and stash show errors. No dataloss AFAICS (though\n> the git stash errors scared me initially).\n>\n> gc and repack error out thus:\n>\n> $ git gc\n> usage: git-pack-objects [{ -q | --progress | --all-progress }]\n>         [--max-pack-size=N] [--local] [--incremental]\n>         [--window=N] [--window-memory=N] [--depth=N]\n>         [--no-reuse-delta] [--no-reuse-object] [--delta-base-offset]\n>         [--threads=N] [--non-empty] [--revs [--unpacked | --all]*] [--reflog]\n>         [--stdout | base-name] [--keep-unreachable] [<ref-list | <object-list]\n> error: failed to run repack\n> $ echo $?\n> 255\n\n\"type --all git\"?\n\"git --exec-path\"?\n\"ls $(git --exec-path)\"?\n"},{"id":"114896","messageId":"46a038f90905280022s1c07565bnf26335fccf7c7e94@mail.gmail.com","threadId":"19552","inReplyTo":"7vprdthezg.fsf@alter.siamese.dyndns.org","subject":"Re: Strangely hosed git install","fromName":"Martin Langhoff","fromEmail":"martin.langhoff@gmail.com","sentAt":"2009-05-28T07:22:13Z","receivedAt":"2009-05-28T07:22:13Z","isPatch":false,"sender":{"key":"martin.langhoff@gmail.com","avatar":"https://gravatar.com/avatar/1e3f311b6c4c15836501901ca58f8c0b0667246488084ba524d8bc9867e22fd9?d=mp&s=160"},"body":"On Thu, May 28, 2009 at 9:18 AM, Junio C Hamano <gitster@pobox.com> wrote:\n> \"type --all git\"?\n> \"git --exec-path\"?\n> \"ls $(git --exec-path)\"?\n>\n\nIt all looks fairly correct to me:\n\n$ type --all git\ngit is /home/martin/bin/git\n$ git --exec-path\n/home/martin/libexec/git-core\n$ ls $(git --ex\nec-path)\ngit                    git-merge-index\ngit-add                git-merge-octopus\ngit-add--interactive   git-merge-one-file\ngit-am                 git-merge-ours\ngit-annotate           git-merge-recursive\ngit-apply              git-merge-resolve\ngit-archimport         git-merge-stupid\ngit-archive            git-merge-subtree\ngit-bisect             git-mergetool\ngit-bisect--helper     git-mergetool--lib\ngit-blame              git-merge-tree\ngit-branch             git-mktag\ngit-bundle             git-mktree\ngit-cat-file           git-mv\ngit-check-attr         git-name-rev\ngit-checkout           git-pack-objects\ngit-checkout-index     git-pack-redundant\ngit-check-ref-format   git-pack-refs\ngit-cherry             git-parse-remote\ngit-cherry-pick        git-patch-id\ngit-citool             git-peek-remote\ngit-clean              git-prune\ngit-clone              git-prune-packed\ngit-commit             git-pull\ngit-commit-tree        git-push\ngit-config             git-quiltimport\ngit-count-objects      git-read-tree\ngit-cvsexportcommit    git-rebase\ngit-cvsimport          git-rebase--interactive\ngit-cvsserver          git-receive-pack\ngit-daemon             git-reflog\ngit-describe           git-relink\ngit-diff               git-remote\ngit-diff-files         git-repack\ngit-diff-index         git-repo-config\ngit-difftool           git-request-pull\ngit-difftool--helper   git-rerere\ngit-diff-tree          git-reset\ngit-fast-export        git-revert\ngit-fast-import        git-rev-list\ngit-fetch              git-rev-parse\ngit-fetch-pack         git-rm\ngit-fetch--tool        git-send-email\ngit-filter-branch      git-send-pack\ngit-fmt-merge-msg      git-shell\ngit-for-each-ref       git-shortlog\ngit-format-patch       git-show\ngit-fsck               git-show-branch\ngit-fsck-objects       git-show-index\ngit-gc                 git-show-ref\ngit-get-tar-commit-id  git-sh-setup\ngit-grep               git-stage\ngit-gui                git-stash\ngit-gui--askpass       git-status\ngit-hash-object        git-stripspace\ngit-help               git-submodule\ngit-help--browse       git-svn\ngit-http-fetch         git-symbolic-ref\ngit-http-push          git-tag\ngit-imap-send          git-tar-tree\ngit-index-pack         git-unpack-file\ngit-init               git-unpack-objects\ngit-init-db            git-update-index\ngit-instaweb           git-update-ref\ngit-log                git-update-server-info\ngit-lost-found         git-upload-archive\ngit-ls-files           git-upload-pack\ngit-ls-remote          git-var\ngit-ls-tree            git-verify-pack\ngit-mailinfo           git-verify-tag\ngit-mailsplit          git-web--browse\ngit-merge              git-whatchanged\ngit-merge-base         git-write-tree\ngit-merge-file\n\ncheers,\n\n\nm\n-- \n martin.langhoff@gmail.com\n martin@laptop.org -- School Server Architect\n - ask interesting questions\n - don't get distracted with shiny stuff  - working code first\n - http://wiki.laptop.org/go/User:Martinlanghoff\n"},{"id":"114904","messageId":"4A1E4B82.9040809@drmicha.warpmail.net","threadId":"19552","inReplyTo":"46a038f90905280022s1c07565bnf26335fccf7c7e94@mail.gmail.com","subject":"Re: Strangely hosed git install","fromName":"Michael J Gruber","fromEmail":"git@drmicha.warpmail.net","sentAt":"2009-05-28T08:29:54Z","receivedAt":"2009-05-28T08:29:54Z","isPatch":false,"sender":{"key":"git@grubix.eu","avatar":"https://avatars.githubusercontent.com/u/233215?v=4"},"body":"Martin Langhoff venit, vidit, dixit 28.05.2009 09:22:\n> On Thu, May 28, 2009 at 9:18 AM, Junio C Hamano <gitster@pobox.com> wrote:\n>> \"type --all git\"?\n>> \"git --exec-path\"?\n>> \"ls $(git --exec-path)\"?\n>>\n> \n> It all looks fairly correct to me:\n\nYes, but your shell seems to find git-diff somewhere, so what about:\n\ntype --all git-diff\necho $PATH\n\nIn any case, Ubuntu seems to do something strange about binaries which\nused to be installed. How can \"git-diff\" trigger a message about\n\"apt-get install git-core\"?\n\nFor sure it does the same strange thing for everything else which used\nto be in your PATH, and this makes current stash, gc etc. fail when\ntrying to call git-pack-objects and such. A \"/usr/bin time machine\"???\n\nOTOH: The git-pack-objects usage line indicates that you clearly have\nolder plumbing lying around. I suspect there are at least 2 issues on\nthat box.\n\nMichael\n"},{"id":"114909","messageId":"46a038f90905280234h35b9b90fwfc52434cd056578e@mail.gmail.com","threadId":"19552","inReplyTo":"4A1E4B82.9040809@drmicha.warpmail.net","subject":"Re: Strangely hosed git install","fromName":"Martin Langhoff","fromEmail":"martin.langhoff@gmail.com","sentAt":"2009-05-28T09:34:33Z","receivedAt":"2009-05-28T09:34:33Z","isPatch":false,"sender":{"key":"martin.langhoff@gmail.com","avatar":"https://gravatar.com/avatar/1e3f311b6c4c15836501901ca58f8c0b0667246488084ba524d8bc9867e22fd9?d=mp&s=160"},"body":"On Thu, May 28, 2009 at 10:29 AM, Michael J Gruber\n<git@drmicha.warpmail.net> wrote:\n> Yes, but your shell seems to find git-diff somewhere, so what about:\n>\n> type --all git-diff\n> echo $PATH\n\n$ type --all git-diff\nbash: type: git-diff: not found\n$ echo $PATH\n/home/martin/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games\n\nthere is _no other_ git-diff. It's bash magic. See\nhttp://popey.com/command_not_found\n\nNote that all the key commands work. I clone, diff, commit, push,\nmerge daily on this machine.\n\n> OTOH: The git-pack-objects usage line indicates that you clearly have\n> older plumbing lying around. I suspect there are at least 2 issues on\n> that box.\n\nMight be. Maybe ~/bin got cleaned up but not libexec? Or the bisecting\nback-and-forth left stray bits in ~/bin?\n\ncheers,\n\n\n\nm\n-- \n martin.langhoff@gmail.com\n martin@laptop.org -- School Server Architect\n - ask interesting questions\n - don't get distracted with shiny stuff  - working code first\n - http://wiki.laptop.org/go/User:Martinlanghoff\n"},{"id":"114910","messageId":"46a038f90905280239q5d8777c4t5fae8cec3c5c9814@mail.gmail.com","threadId":"19552","inReplyTo":"46a038f90905280234h35b9b90fwfc52434cd056578e@mail.gmail.com","subject":"Re: Strangely hosed git install","fromName":"Martin Langhoff","fromEmail":"martin.langhoff@gmail.com","sentAt":"2009-05-28T09:39:11Z","receivedAt":"2009-05-28T09:39:11Z","isPatch":false,"sender":{"key":"martin.langhoff@gmail.com","avatar":"https://gravatar.com/avatar/1e3f311b6c4c15836501901ca58f8c0b0667246488084ba524d8bc9867e22fd9?d=mp&s=160"},"body":"On Thu, May 28, 2009 at 11:34 AM, Martin Langhoff\n<martin.langhoff@gmail.com> wrote:\n> Might be. Maybe ~/bin got cleaned up but not libexec? Or the bisecting\n> back-and-forth left stray bits in ~/bin?\n\nThe problem was with a polluted libexec. Clearing/reinstalling git in\nmy ~/bin didn't help, but the same procedure in libexec worked.\n\nMinor note for people bisecting random versions of git :-)\n\n\n\n\nm\n-- \n martin.langhoff@gmail.com\n martin@laptop.org -- School Server Architect\n - ask interesting questions\n - don't get distracted with shiny stuff  - working code first\n - http://wiki.laptop.org/go/User:Martinlanghoff\n"},{"id":"114914","messageId":"4A1E5DBC.2090908@drmicha.warpmail.net","threadId":"19552","inReplyTo":"46a038f90905280234h35b9b90fwfc52434cd056578e@mail.gmail.com","subject":"Re: Strangely hosed git install","fromName":"Michael J Gruber","fromEmail":"git@drmicha.warpmail.net","sentAt":"2009-05-28T09:47:40Z","receivedAt":"2009-05-28T09:47:40Z","isPatch":false,"sender":{"key":"git@grubix.eu","avatar":"https://avatars.githubusercontent.com/u/233215?v=4"},"body":"Martin Langhoff venit, vidit, dixit 28.05.2009 11:34:\n> On Thu, May 28, 2009 at 10:29 AM, Michael J Gruber\n> <git@drmicha.warpmail.net> wrote:\n>> Yes, but your shell seems to find git-diff somewhere, so what about:\n>>\n>> type --all git-diff\n>> echo $PATH\n> \n> $ type --all git-diff\n> bash: type: git-diff: not found\n> $ echo $PATH\n> /home/martin/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games\n> \n> there is _no other_ git-diff. It's bash magic. See\n> http://popey.com/command_not_found\n\nThis is insane. Don't they even distinguish between an interactive shell\nand a non-interactive one?\n\n> \n> Note that all the key commands work. I clone, diff, commit, push,\n> merge daily on this machine.\n> \n>> OTOH: The git-pack-objects usage line indicates that you clearly have\n>> older plumbing lying around. I suspect there are at least 2 issues on\n>> that box.\n> \n> Might be. Maybe ~/bin got cleaned up but not libexec? Or the bisecting\n> back-and-forth left stray bits in ~/bin?\n\nWell, I would say go \"find / git-diff-index\", or simply nuke anything\ngit you find and do a clean install... \"find\"ing the left over bits\nwould help making sure that git's own search path is OK.\n\nMichael\n"},{"id":"114915","messageId":"46a038f90905280311p406a528atb8d21a30fe53b0e3@mail.gmail.com","threadId":"19552","inReplyTo":"4A1E5DBC.2090908@drmicha.warpmail.net","subject":"Re: Strangely hosed git install","fromName":"Martin Langhoff","fromEmail":"martin.langhoff@gmail.com","sentAt":"2009-05-28T10:11:01Z","receivedAt":"2009-05-28T10:11:01Z","isPatch":false,"sender":{"key":"martin.langhoff@gmail.com","avatar":"https://gravatar.com/avatar/1e3f311b6c4c15836501901ca58f8c0b0667246488084ba524d8bc9867e22fd9?d=mp&s=160"},"body":"On Thu, May 28, 2009 at 11:47 AM, Michael J Gruber\n<git@drmicha.warpmail.net> wrote:\n> This is insane. Don't they even distinguish between an interactive shell\n> and a non-interactive one?\n\nYes they do. I mentioned it but I didn't think it was the reason\nbehind the problem.\n\n> Well, I would say go \"find / git-diff-index\", or simply nuke anything\n> git you find and do a clean install... \"find\"ing the left over bits\n> would help making sure that git's own search path is OK.\n\nwell, that's not what happens when people bisect back and forth. It\nused to be reasonably safe, it got unsafe when we moved lots of things\nto libexec (and therefore the make install target got a nice warning\nmessage about it). Now there might something acting up again.\n\nAlas, I didn't keep a backup of my libexec :-/\n\n\n\n\nm\n-- \n martin.langhoff@gmail.com\n martin@laptop.org -- School Server Architect\n - ask interesting questions\n - don't get distracted with shiny stuff  - working code first\n - http://wiki.laptop.org/go/User:Martinlanghoff\n"}]}