strange error while pushing

I was going to push some stuff I'm working on to my repo at repo.or.cz, and just got the following error:

$ GIT_TRACE=1 git push kusma work/daemon-win32:work/daemon-win32-process
trace: built-in: git 'push' 'kusma'
'work/daemon-win32:work/daemon-win32-process'
trace: run_command: 'ssh' 'repo.or.cz' 'git-receive-pack
'\''/srv/git/git/kusma.git'\'''
trace: run_command: 'pack-objects' '--all-progress-implied' '--revs'
'--stdout' '--thin'
trace: built-in: git 'pack-objects' '--all-progress-implied' '--revs'
'--stdout' '--thin'
usage: git pack-objects [{ -q | --progress | --all-progress }]
        [--max-pack-size=N] [--local] [--incremental]
        [--window=N] [--window-memory=N] [--depth=N]
        [--no-reuse-delta] [--no-reuse-object] [--delta-base-offset]
        [--threads=N] [--non-empty] [--revs [--unpacked | --all]*] [--reflog]
        [--stdout | base-name] [--include-tag]
        [--keep-unreachable | --unpack-unreachable]
        [<ref-list | <object-list]
error: pack-objects died with strange error
error: failed to push some refs to 'ssh://repo.or.cz/srv/git/git/kusma.git'
$ git --version
git version 1.6.6.rc2.5.g49666

Is this something anyone have experienced before?

I'm not entirely sure if this happens on the local side or the remote side... I've tried with a few different versions locally but the issue seems to persist, so I'm starting to suspect it's an issue at the remote end. Any insight, anyone?

On Sun, Dec 13, 2009 at 11:41 PM, Erik Faye-Lund <kusmabite@googlemail.com> wrote:

Pushing to github gives the same error, so I guess it's a local thing. I'll check some older versions.

On Sun, Dec 13, 2009 at 11:41:49PM +0100, Erik Faye-Lund wrote:

I notice your pack-objects is being called with the new --all-progress-implied, and then you get a usage error with pack-objects:

Is it possible you have a new git accidentally calling an old version of pack-objects?

-Peff

On Mon, Dec 14, 2009 at 12:02 AM, Jeff King <peff@peff.net> wrote:

Ah, yes it is! I just now tracked down the issue myself, and landed at the same conclution. The reason? Simple, I was pushing git from a directory with a recent git-binary, when my *installed* git was v1.6.4 ;)

Running "make install" before pushing fixed the issue.

Thanks for wasting time on my PEBCAK :)

Heya,

On Mon, Dec 14, 2009 at 00:08, Erik Faye-Lund <kusmabite@googlemail.com> wrote:

Isn't this the reason most people don't have "." in their PATH? :P

Hi,

On Mon, 14 Dec 2009, Sverre Rabbelier wrote:

Try removing "." from the PATH on Windows... to spare you some cycles: it is in PATH _implicitly_. You cannot remove it from ".", even if you try hard.

Ciao, Dscho

Heya,

On Mon, Dec 14, 2009 at 12:35, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:

It's an amazing OS, it's quirks keep surprising me day after day :).