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

Re: ISSUE - Sequential execution failure - Lock auto created between git commands

From
Patrick Steinhardt <ps@pks.im>
Date
May 26, 2025, 13:23 UTC
Message-ID
<aDRrO4x0o0Hit6au@pks.im>
In-Reply-To
<CAJR-fbZ4X1+gN75m2dUvocR6NkowLOZ9F26cjBy8w1qd181OoQ@mail.gmail.com>
On Sun, May 25, 2025 at 05:13:30PM +0300, Yonatan Roth wrote:
Show 29 quoted lines
> Hi,
> 
> 
> Using a script we run the following set of git commands:
> 
> git branch -a
> 
> git remote -v
> 
> git stash push --all --include-untracked
> 
> git checkout test_git_ver
> 
> git remote -v
> 
> git fetch
> 
> git status --branch --porcelain=v1 -u
> 
> git checkout test_git_ver_workspace
> 
> 
> 
> 
> After upgrading the git version to - *2.47.2*, we started getting the
> following error:
> 
> error: cannot lock ref 'HEAD': Unable to create '.../.git/*HEAD.lock*':
> File exists.

This sounds similar to the issue reported in [1], please see my reply there. I'll send a patch series the over the next days to address the issue.

Patrick
[1]: <CANi7bVAkNc+gY1NoXfJuDRjxjZLTgL8Lfn8_ZmWsvLAoiLPkNg@mail.gmail.com>
Previous: Yonatan Roth
Message 2 of 2 in “ISSUE - Sequential execution failure - Lock auto created between git commands”
  1. Yonatan RothMay 25, 2025
  2. Patrick SteinhardtMay 26, 2025

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.