Thanks a lot for replying!
That exactly was the problem. We've configured gitosis to allow access
over 'ssh://' (Read / Write) while 'git://' access was limited (Read
only).
Changing the configuration worked out just fine.
-Thanks & Regards,
Sitesh
On Tue, Nov 5, 2013 at 4:33 AM, Jeff King wrote:
> On Fri, Nov 01, 2013 at 04:02:10PM +0530, Sitesh Shrivastava wrote:
>
>> I'm using a gitosis server. Suddenly I'm not able to push to the
>> remote server. Everyone else is able to push to the same server. Btw I
>> can't push to *any repo* on the server. This is the error I get:
>>
>> Counting objects: 5, done.
>> Delta compression using up to 4 threads.
>> Compressing objects: 100% (3/3), done.
>> Writing objects: 100% (3/3), 353 bytes | 0 bytes/s, done.
>> Total 3 (delta 1), reused 0 (delta 0)
>> error: unpack failed: unpack-objects abnormal exit
>> To git://git.srv.net/code-repo.git
>> ! [remote rejected] master -> master (n/a (unpacker error))
>> error: failed to push some refs to 'git://git.srv.net/code-repo.git'
>
> You are trying to push over the "git://" protocol. That isn't enabled by
> default (because it has no authentication at all). Did you enable it? If
> so, does the user running git-daemon have permission to write to the
> repository?
>
> The server notes that unpack-objects fails, but in older git versions
> the stderr of unpack-objects does not get sent to the client. If your
> git-daemon process is logging somewhere, you might check that log for
> more details.
>
> Since v1.7.12.3, that output is sent over the sideband channel to the
> client. So another option is to upgrade the version of git on the
> server.
>
>> Can something be wrong with my git installation?
>> git --version
>> git version 1.8.3.2
>
> That's your client version. The server version is older than that (in
> v1.7.12.3, the unpacker error message also dropped the "n/a" bit, so the
> output above comes from a server older than that).
>
> -Peff
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
