Re: "lock file exists" when fetching in bare clone of repository

From: Junio C Hamano <gitster@pobox.com>
Date: Aug 21, 2025, 16:05 UTC
Message-ID: <xmqqwm6w3bjp.fsf@gitster.g>
In-Reply-To: <aKbwabLZiWasYoBC@pks.im>

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.

Show 13 quoted lines

>     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