# strange error while pushing

7 messages from 2009-12-13 to 2009-12-14. Participants: Erik Faye-Lund, Jeff King, Sverre Rabbelier, Johannes Schindelin.
Thread: https://gitlist.dev/t/21945

## Erik Faye-Lund, 2009-12-13 22:41

Subject: strange error while pushing
Message-ID: <40aa078e0912131441i370d9c23r65c42fe1f46bd194@mail.gmail.com>
URL: https://gitlist.dev/e/40aa078e0912131441i370d9c23r65c42fe1f46bd194%40mail.gmail.com

```
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?

-- 
Erik "kusma" Faye-Lund

```

## Erik Faye-Lund, 2009-12-13 22:57

Subject: Re: strange error while pushing
Message-ID: <40aa078e0912131457ge5ee47j6d436e1fb73b9d37@mail.gmail.com>
URL: https://gitlist.dev/e/40aa078e0912131457ge5ee47j6d436e1fb73b9d37%40mail.gmail.com
In-Reply-To: <40aa078e0912131441i370d9c23r65c42fe1f46bd194@mail.gmail.com>

```
On Sun, Dec 13, 2009 at 11:41 PM, Erik Faye-Lund
<kusmabite@googlemail.com> wrote:
> 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?

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

-- 
Erik "kusma" Faye-Lund

```

## Jeff King, 2009-12-13 23:02

Subject: Re: strange error while pushing
Message-ID: <20091213230214.GA27365@sigill.intra.peff.net>
URL: https://gitlist.dev/e/20091213230214.GA27365%40sigill.intra.peff.net
In-Reply-To: <40aa078e0912131441i370d9c23r65c42fe1f46bd194@mail.gmail.com>

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

> 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'

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

> 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]

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

-Peff

```

## Erik Faye-Lund, 2009-12-13 23:08

Subject: Re: strange error while pushing
Message-ID: <40aa078e0912131508y79815bej6290c0848aa9f9cf@mail.gmail.com>
URL: https://gitlist.dev/e/40aa078e0912131508y79815bej6290c0848aa9f9cf%40mail.gmail.com
In-Reply-To: <20091213230214.GA27365@sigill.intra.peff.net>

```
On Mon, Dec 14, 2009 at 12:02 AM, Jeff King <peff@peff.net> wrote:
> On Sun, Dec 13, 2009 at 11:41:49PM +0100, Erik Faye-Lund wrote:
>> 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]
>
> Is it possible you have a new git accidentally calling an old version of
> pack-objects?
>

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 :)

-- 
Erik "kusma" Faye-Lund

```

## Sverre Rabbelier, 2009-12-14 00:01

Subject: Re: strange error while pushing
Message-ID: <fabb9a1e0912131601q71dcb4c4h2fafa03df14be3c1@mail.gmail.com>
URL: https://gitlist.dev/e/fabb9a1e0912131601q71dcb4c4h2fafa03df14be3c1%40mail.gmail.com
In-Reply-To: <40aa078e0912131508y79815bej6290c0848aa9f9cf@mail.gmail.com>

```
Heya,

On Mon, Dec 14, 2009 at 00:08, Erik Faye-Lund <kusmabite@googlemail.com> wrote:
> Simple, I was pushing git from a
> directory with a recent git-binary, when my *installed* git was v1.6.4

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


-- 
Cheers,

Sverre Rabbelier

```

## Sverre Rabbelier, 2009-12-14 11:33

Subject: Re: strange error while pushing
Message-ID: <fabb9a1e0912140333m5b13f6beke5010eea9f77df84@mail.gmail.com>
URL: https://gitlist.dev/e/fabb9a1e0912140333m5b13f6beke5010eea9f77df84%40mail.gmail.com
In-Reply-To: <alpine.DEB.1.00.0912141235090.4985@pacific.mpi-cbg.de>

```
Heya,

On Mon, Dec 14, 2009 at 12:35, Johannes Schindelin
<Johannes.Schindelin@gmx.de> 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.

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

-- 
Cheers,

Sverre Rabbelier

```

## Johannes Schindelin, 2009-12-14 11:35

Subject: Re: strange error while pushing
Message-ID: <alpine.DEB.1.00.0912141235090.4985@pacific.mpi-cbg.de>
URL: https://gitlist.dev/e/alpine.DEB.1.00.0912141235090.4985%40pacific.mpi-cbg.de
In-Reply-To: <fabb9a1e0912131601q71dcb4c4h2fafa03df14be3c1@mail.gmail.com>

```
Hi,

On Mon, 14 Dec 2009, Sverre Rabbelier wrote:

> On Mon, Dec 14, 2009 at 00:08, Erik Faye-Lund <kusmabite@googlemail.com> 
> wrote:
> > Simple, I was pushing git from a directory with a recent git-binary, 
> > when my *installed* git was v1.6.4
> 
> Isn't this the reason most people don't have "." in their PATH? :P

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

```
