{"thread":{"id":"21945","subject":"strange error while pushing","startedAt":"2009-12-13T22:41:49Z","lastAt":"2009-12-14T11:35:52Z","messageCount":7,"participants":["Erik Faye-Lund","Jeff King","Sverre Rabbelier","Johannes Schindelin"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"129816","messageId":"40aa078e0912131441i370d9c23r65c42fe1f46bd194@mail.gmail.com","threadId":"21945","inReplyTo":null,"subject":"strange error while pushing","fromName":"Erik Faye-Lund","fromEmail":"kusmabite@googlemail.com","sentAt":"2009-12-13T22:41:49Z","receivedAt":"2009-12-13T22:41:49Z","isPatch":false,"sender":{"key":"kusmabite@gmail.com","avatar":"https://avatars.githubusercontent.com/u/47073?v=4"},"body":"I was going to push some stuff I'm working on to my repo at\nrepo.or.cz, and just got the following error:\n\n$ GIT_TRACE=1 git push kusma work/daemon-win32:work/daemon-win32-process\ntrace: built-in: git 'push' 'kusma'\n'work/daemon-win32:work/daemon-win32-process'\ntrace: run_command: 'ssh' 'repo.or.cz' 'git-receive-pack\n'\\''/srv/git/git/kusma.git'\\'''\ntrace: run_command: 'pack-objects' '--all-progress-implied' '--revs'\n'--stdout' '--thin'\ntrace: built-in: git 'pack-objects' '--all-progress-implied' '--revs'\n'--stdout' '--thin'\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] [--include-tag]\n [--keep-unreachable | --unpack-unreachable]\n [ wrote:\n> I'm not entirely sure if this happens on the local side or the remote\n> side... I've tried with a few different versions locally but the issue\n> seems to persist, so I'm starting to suspect it's an issue at the\n> remote end. Any insight, anyone?\n\nPushing to github gives the same error, so I guess it's a local thing.\nI'll check some older versions.\n\n-- \nErik \"kusma\" Faye-Lund\n"},{"id":"129820","messageId":"20091213230214.GA27365@sigill.intra.peff.net","threadId":"21945","inReplyTo":"40aa078e0912131441i370d9c23r65c42fe1f46bd194@mail.gmail.com","subject":"Re: strange error while pushing","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2009-12-13T23:02:14Z","receivedAt":"2009-12-13T23:02:14Z","isPatch":false,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Sun, Dec 13, 2009 at 11:41:49PM +0100, Erik Faye-Lund wrote:\n\n> I was going to push some stuff I'm working on to my repo at\n> repo.or.cz, and just got the following error:\n> \n> $ GIT_TRACE=1 git push kusma work/daemon-win32:work/daemon-win32-process\n> trace: built-in: git 'push' 'kusma'\n> 'work/daemon-win32:work/daemon-win32-process'\n> trace: run_command: 'ssh' 'repo.or.cz' 'git-receive-pack\n> '\\''/srv/git/git/kusma.git'\\'''\n> trace: run_command: 'pack-objects' '--all-progress-implied' '--revs'\n> '--stdout' '--thin'\n> trace: built-in: git 'pack-objects' '--all-progress-implied' '--revs'\n> '--stdout' '--thin'\n\nI notice your pack-objects is being called with the new\n--all-progress-implied, and then you get a usage error with\npack-objects:\n\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] [--include-tag]\n> [--keep-unreachable | --unpack-unreachable]\n> [ wrote:\n> On Sun, Dec 13, 2009 at 11:41:49PM +0100, Erik Faye-Lund wrote:\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] [--include-tag]\n>>         [--keep-unreachable | --unpack-unreachable]\n>>         [\n> Is it possible you have a new git accidentally calling an old version of\n> pack-objects?\n>\n\nAh, yes it is! I just now tracked down the issue myself, and landed at\nthe same conclution. The reason? Simple, I was pushing git from a\ndirectory with a recent git-binary, when my *installed* git was v1.6.4\n;)\n\nRunning \"make install\" before pushing fixed the issue.\n\nThanks for wasting time on my PEBCAK :)\n\n-- \nErik \"kusma\" Faye-Lund\n"},{"id":"129825","messageId":"fabb9a1e0912131601q71dcb4c4h2fafa03df14be3c1@mail.gmail.com","threadId":"21945","inReplyTo":"40aa078e0912131508y79815bej6290c0848aa9f9cf@mail.gmail.com","subject":"Re: strange error while pushing","fromName":"Sverre Rabbelier","fromEmail":"srabbelier@gmail.com","sentAt":"2009-12-14T00:01:33Z","receivedAt":"2009-12-14T00:01:33Z","isPatch":false,"sender":{"key":"srabbelier@gmail.com","avatar":"https://avatars.githubusercontent.com/u/3098?v=4"},"body":"Heya,\n\nOn Mon, Dec 14, 2009 at 00:08, Erik Faye-Lund wrote:\n> Simple, I was pushing git from a\n> directory with a recent git-binary, when my *installed* git was v1.6.4\n\nIsn't this the reason most people don't have \".\" in their PATH? :P\n\n\n-- \nCheers,\n\nSverre Rabbelier\n"},{"id":"129863","messageId":"fabb9a1e0912140333m5b13f6beke5010eea9f77df84@mail.gmail.com","threadId":"21945","inReplyTo":"alpine.DEB.1.00.0912141235090.4985@pacific.mpi-cbg.de","subject":"Re: strange error while pushing","fromName":"Sverre Rabbelier","fromEmail":"srabbelier@gmail.com","sentAt":"2009-12-14T11:33:28Z","receivedAt":"2009-12-14T11:33:28Z","isPatch":false,"sender":{"key":"srabbelier@gmail.com","avatar":"https://avatars.githubusercontent.com/u/3098?v=4"},"body":"Heya,\n\nOn Mon, Dec 14, 2009 at 12:35, Johannes Schindelin\n wrote:\n> Try removing \".\" from the PATH on Windows... to spare you some cycles: it\n> is in PATH _implicitly_.  You cannot remove it from \".\", even if you try\n> hard.\n\nIt's an amazing OS, it's quirks keep surprising me day after day :).\n\n-- \nCheers,\n\nSverre Rabbelier\n"},{"id":"129862","messageId":"alpine.DEB.1.00.0912141235090.4985@pacific.mpi-cbg.de","threadId":"21945","inReplyTo":"fabb9a1e0912131601q71dcb4c4h2fafa03df14be3c1@mail.gmail.com","subject":"Re: strange error while pushing","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2009-12-14T11:35:52Z","receivedAt":"2009-12-14T11:35:52Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi,\n\nOn Mon, 14 Dec 2009, Sverre Rabbelier wrote:\n\n> On Mon, Dec 14, 2009 at 00:08, Erik Faye-Lund \n> wrote:\n> > Simple, I was pushing git from a directory with a recent git-binary, \n> > when my *installed* git was v1.6.4\n> \n> Isn't this the reason most people don't have \".\" in their PATH? :P\n\nTry removing \".\" from the PATH on Windows... to spare you some cycles: it \nis in PATH _implicitly_. You cannot remove it from \".\", even if you try \nhard.\n\nCiao,\nDscho\n"}]}