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

failed to lock

From
Jay Soffian <jaysoffian@gmail.com>
Date
Apr 14, 2010, 20:49 UTC
Message-ID
<j2o76718491004141349l53b53347v7f4c0edcab69e4c2@mail.gmail.com>
With git-1.7, I regularly get this when pushing to a non-bare repo:
remote: error: failed to lock refs/remotes/origin/master
...
 ! [remote rejected] origin/master -> origin/master (failed to lock)
error: failed to push some refs to 'ssh://remote/repo'

I see this pushing from a Mac, to either a Mac or to Cygwin. I have seen it on various versions of the 1.7 series and possibly before. In the instance above:

local git version 1.7.0.3.436.g2b878 remote git version 1.7.0.3

In addition, the ref is (apparently) updated just fine. If I push a second time, no update occurs.

The problem is reproducible. Any idea where I should start debugging it?
j.
Next: Jay Soffian
Message 1 of 6 in “failed to lock”
  1. Jay SoffianApr 14, 2010
  2. Jay SoffianApr 14, 2010
  3. Jay SoffianApr 15, 2010
  4. Junio C HamanoApr 15, 2010
  5. Jay SoffianApr 15, 2010
  6. Junio C HamanoApr 15, 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.