1

我一直致力于通过使用 Paramiko 作为 Git 的 SSH 桥来设置 git 服务器。我能够毫无问题地克隆我的存储库,甚至可以推送更改,但是我收到一条烦人的错误消息。

Pushing to git@localhost:/pckprojects/heyworld
Counting objects: 5, done.
Delta compression using up to 2 threads.
Compressing objects: 100% (2/2), done.
Writing objects: 100% (3/3), 262 bytes, done.
Total 3 (delta 1), reused 0 (delta 0)
To git@localhost:/pckprojects/heyworld
     348dfdc..1c0468e  master -> master
updating local tracking ref 'refs/remotes/origin/master'
error: failed to push some refs to 'git@localhost:/pckprojects/heyworld'

我的 git 的配置如下所示:

[core]
    repositoryformatversion = 0
    filemode = true
    bare = true
    sharedRepository = all
[receive]
    denyNonFastForwards = false
    denyCurrentBranch = false
    denyDeletes = false

奇怪的是“master”实际上确实得到了更新,而且我在存储库中没有其他分支。此外,如果我从磁盘克隆/推送存储库而不是通过 SSH,我看不到任何错误。

有人对我为什么会看到此错误有任何想法吗?

谢谢...

编辑:

由于我的问题似乎与我的 SSH 服务器有关,因此主循环如下:

        proc = subprocess.Popen(command, stdin=subprocess.PIPE,
                stdout=subprocess.PIPE, stderr=subprocess.PIPE)

        while True:
            try:
                r_ready, w_ready, x_ready = select.select(
                    [channel, proc.stdout, proc.stderr], [proc.stdin], [])
            except Exception, e:
                print e
                print 'channel: ' + str(channel)
                print 'proc: ' + str(proc)

            if channel in r_ready and channel.recv_ready():
                data = channel.recv(128)
                if len(data) > 0:
                    print 'IN>channel ' + repr(data)
                    proc.stdin.write(data)
                else:
                    pass

            if proc.stdout in r_ready:  
                data = proc.stdout.read(1)
                channel.sendall(data)

            if proc.stderr in r_ready:

                data = proc.stdout.read(1)
                if len(data) > 0:
                    channel.sendall(data)

                else:
                    print "Encountered empty stderr, breaking"
                    break                       

        print 'will close'
        channel.shutdown(2)
        channel.close()

更多信息

我认为查看实际交流可能会有所帮助。它出现在服务器端,因为 git 客户端不允许您看到这么多。

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
4

2 回答 2

0

A very helpful user on the git mailing list took what he thought was a stab in the dark and got it right.

I wasn't returning the exit code, which Git expects on pushes. That solved the problem.

于 2010-07-21T22:34:41.617 回答
0

您可能知道,这可能是一堆问题!

  • 我最初的猜测是服务器上的某些权限不正确,因此无法更新一些非关键信息
  • 也可能是其他一些问题...

几个快速的问题/建议:

  • 可以手动成功运行命令吗?
  • 尝试将 --verbose 标志添加到推送命令(即 git push --verbose origin/master)

添加详细标志可能会让您快速解决问题。

于 2010-07-17T22:25:58.623 回答