Re: [remote rejected] master -> master (n/a (unpacker error))

From: Chris Packham <judge.packham@gmail.com>
Date: May 13, 2010, 00:06 UTC
Message-ID: <AANLkTilfXLdYCIZAu_I5vGTrbI08fbqUpIsjx5yP1q47@mail.gmail.com>
In-Reply-To: <AANLkTinV2U6Lbbl0N7jVAESEi0mZQ_D3slMEYa68vRT4@mail.gmail.com>

On Wed, May 12, 2010 at 12:45 PM, Robert Buck <buck.robert.j@gmail.com> wrote:

Show 23 quoted lines

> Today, just after someone else committed to my public repository I
> started getting errors. Until then Git worked great.
>
> Does anyone know what is going on here? Are there particular versions
> of Git with known issues around this?
>
>
> uname@hostname:~/dev/workspaces/scm-evaluations/welcome.git/install/git-config$
> git push
> Counting objects: 7, done.
> Delta compression using up to 2 threads.
> Compressing objects: 100% (4/4), done.
> Writing objects: 100% (4/4), 922 bytes, done.
> Total 4 (delta 0), reused 4 (delta 0)
> error: unable to create temporary sha1 filename ./objects/e6: File
> exists
>
> fatal: failed to write object
> error: unpack failed: unpacker exited with error code
> To ssh://git.projectbedrock.com/var/cache/git/welcome.git
>  ! [remote rejected] master -> master (n/a (unpacker error))
> error: failed to push some refs to
> 'ssh://git.projectbedrock.com/var/cache/git/welcome.git'

This is probably a permissions problem on the server. We use git over ssh at $dayjob and we need to make sure everyone who pushes to a repository on the server is a member of the same group and that the repositories are created with "git init --shared" otherwise we run into problems like this. Its not too much of an issue for us because we have a maintainer model and the maintainers generally have the right permissions and don't change frequently.

I think the "shared" part is probably the problem in this case because you can both obviously create files on the server. Rhe problem appears to be when one of you needs to update a file (or directory) the other created.

To fix your current problem you'll just need to ssh into that server and find the welcome.git/objects directory and check the permissions on the "e6" directory and its contents. You will keep running into this problem until the permissions/sharing is sorted. Theres probably a config variable which dictates the permissions to use when creating objects on the server which is changed when you pass the "--shared" option to "git init", but I'm not sure what its is (I see some man pages in your future).

> As an aside, where the heck is the git bug tracker? I've searched, and
> searched, and ... All I found is a Debian tracking system, which
> appears to have no full text search capabilities.

You're looking at it bugs, patches, questions all go to this mailing list. The archive on gmane[1] is conveniently search-able.

[1] http://news.gmane.org/gmane.comp.version-control.git