git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Git & Paramiko: failed to push some refs to ...

From
PKPhilip Kimmey <philip.kimmey@gmail.com>
Date
Jul 20, 2010, 00:20 UTC
Message-ID
<AANLkTil0soA4pLGRZT-jgdOkB3s8qApG_h2a-UW2P_G5@mail.gmail.com>

If you prefer you can see the outline of my question at stackoverflow, with better formatting than e-mail will afford:

http://stackoverflow.com/questions/3262161/git-failed-to-push-some-refs-to-with-custom-git-bridge

I am writing a Python ssh server using Paramiko. While it is very powerful software, when using it to push git repositories, I run into strange errors. The following is git's output on the client machine.

$ git push origin master
Counting objects: 5, done.
Delta compression using up to 2 threads.
Compressing objects: 100% (2/2), done.
Writing objects: 100% (3/3), 263 bytes, done.
Total 3 (delta 1), reused 0 (delta 0)
To git@localhost:/pckprojects/heyworld/
   d83f744..404debd  master -> master
error: failed to push some refs to 'git@localhost:/pckprojects/heyworld/'

From the server side I have enough print statements to see the entire transaction, which looks something like this:

git-receive-pack /home/www/data/project/heyworld/

OUT >> 00721ee2436e45c80236878132dc87d9e9fee6a81de5 refs/heads/master\x00 report-status delete-refs side-band-64k ofs-delta\n0000

IN >> 00841ee2436e45c80236878132dc87d9e9fee6a81de5 6054b3358787bafd1d96c0fdfbf016d620ccdf09 refs/heads/master\x00 report-status side-band-64k0000

IN >> PACK\x00\x00\x00\x02\x00\x00\x00\x03\x96\x0ex\x9c\xa5\x8cM\x0e\xc2 \x14\x06\xf7\x9c\x82\x0b\xd8<(?\x8f\xc4\x18\xf7n\xbc\x02\xc2\x87%\x16\xdb4\xb8\xf0\xf66\xbd\x82\xcb\x99d\xa6o\x80\x846\xd9!)\x1b\x0b\xb1\r1$dO\x05\xa6\xb0\xa3@\x06%D<\xb2\x16k\xdc\xf0\xeeRa/F\x07c\x13\x93\x1e\x1d{V\xa3\xce\x89}\x0e\x08\x05p\x91U\x86\x15\xf1\xd3\xa7e\x93\xf7\xa9\xceu\x95\xb7\xda\x1a\xbe\xf2\xbc\x1e8\xbc\x0e\xbc>[\xac\xf3\x90\x96v\x91J\xfb`X\xb3V\xf2D\x96H\xec\xb6\xd5\xde\xf1\xc7B4,\xe2\x07\xff\x8aF\xba\xaf\x01x\x9c340031Q\xc8H\xaddP\xd8P\xfcmzGg\x8aY\xc4\x8e\xad\xb1<\xca\x1b\xa3\x93\xee\xbd\x05\x00\xa8\xb4\x0c\x9by\xd3\xfe\xa0C\x86fU\x18\xbe\xa5\x86\xac5*\xf7\x11\x89\x8b9$x\x9c\x0b\x8b\x9a\x10\xc6\x92\x9b\x9a\xcf\x05\x00\x0f\xb2\x02\xe6=\x12?\xde\x1f\x9a=v\x0c3c\xf66\xc6\xcc1y\xe4\xb8\xa0

OUT >> 0030\x01000eunpack ok\n009krf/ed/atr0000

CLOSE CONNECTION

This looks healthy to me, but I'm of course not that familiar with the details. In addition, as far as I can tell, master does in fact get updated and everything properly, so I have no idea where that error message is coming from. If I use openssh-server instead of my Paramiko server, the same actions on the client work fine.

Thanks for the help!

Sincerely, Philip Kimmey

Next: Thomas Rast
Message 1 of 3 in “Git & Paramiko: failed to push some refs to ...”
  1. Philip KimmeyJul 20, 2010
  2. Thomas RastJul 20, 2010
  3. Philip KimmeyJul 20, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.