From: Junio C Hamano <gitster@pobox.com>
To: Patrick Steinhardt <ps@pks.im>
Cc: Jeff King <peff@peff.net>, Joe Drew <joe.drew@indexexchange.com>,
"git@vger.kernel.org" <git@vger.kernel.org>,
Karthik Nayak <karthik.188@gmail.com>
Subject: Re: "lock file exists" when fetching in bare clone of repository
Date: Thu, 21 Aug 2025 09:05:30 -0700 [thread overview]
Message-ID: <xmqqwm6w3bjp.fsf@gitster.g> (raw)
In-Reply-To: <aKbwabLZiWasYoBC@pks.im> (Patrick Steinhardt's message of "Thu, 21 Aug 2025 12:09:45 +0200")
Patrick Steinhardt <ps@pks.im> writes:
> You're on a case-insensitive filesystem, and the remote you are
> trying to fetch from has references that only differ in casing. It
> is impossible to store such references with the "files" backend. You
"backend." -> "backend on your system."
> can either accept this as-is, in which case you won't be able to
> store all remote references on disk. Or you can alternatively
I do not see the former as a viable choice, though. When this
happens, the clone or fetch fails and the user cannot catch up to
the upstream development, no? You have to futz with the fetch
refspec to cause refs your filesystem cannot store ignored in order
to make progress on other refs, but that is making the user do more
than accepting this as-is.
> migrate your repository to use the "reftable" backend with the
> following command:
>
> git refs migrate --ref-format=reftable
>
> Please keep in mind that not all implementations of Git support this
> new format yet. So if you use tools other than Git to access this
> repository it may not be an option to migrate to reftables.
>
> The last part is what I'm working on right now. libgit2 is fully
> functional now, but what is still lacking is reviews.
>
> Patrick
next prev parent reply other threads:[~2025-08-21 16:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-20 20:54 "lock file exists" when fetching in bare clone of repository Joe Drew
2025-08-20 21:33 ` Jeff King
2025-08-21 7:15 ` Patrick Steinhardt
2025-08-21 7:27 ` Jeff King
2025-08-21 10:09 ` Patrick Steinhardt
2025-08-21 16:05 ` Junio C Hamano [this message]
2025-08-22 6:13 ` Patrick Steinhardt
2025-08-22 8:01 ` Karthik Nayak
2025-08-22 17:47 ` Junio C Hamano
2025-08-28 13:51 ` Karthik Nayak
2025-08-28 16:16 ` Junio C Hamano
2025-09-01 18:17 ` Karthik Nayak
2025-08-21 15:47 ` Junio C Hamano
2025-08-22 13:28 ` Joe Drew
2025-08-26 11:19 ` Jeff King
2025-09-02 10:55 ` Patrick Steinhardt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqwm6w3bjp.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=joe.drew@indexexchange.com \
--cc=karthik.188@gmail.com \
--cc=peff@peff.net \
--cc=ps@pks.im \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).