bug#65241: 30.0.50; Cannot clone NonGNU ELPA

[Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>]

Stefan Kangas [2023-09-05 16:25:05] wrote:
> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> `git show 2699d230e3b592ae42506d7b5c969a7ac6a4593c` suggests this is
>> part of `coffee-mode`, and indeed:
>>
>>     git -c 'Transfer.fsckObjects=true' clone https://github.com/defunkt/coffee-mode
>>
>> gives me the same warning (tho it's a warning rather than an error).
>>
>> Just use
>>
>>     git -c 'Transfer.fsckObjects=false' clone ...
>>
>> to workaround the problem.  I think the problem is fundamentally in
>> Git's camp: the format that `fsckObjects` enforces is incompatible with
>> the data it used to generate, and since rewriting history is a big
>> problem, it's not something that can be fixed.
>
> I don't think users will realize that, though.  They'll blame us for
> having a broken repository.

Could be, but we (and many other repositories) have lived with it for
several years already.  I think the problem is on Git side: it should be
a warning rather than an error (AFAICT, `git fsck` flagged the problem
as a mere warning).

And indeed, when I try it now, I don't get an error any more, so maybe
it's been fixed in more recent versions of Git?
When you try

    git -c 'Transfer.fsckObjects=true' clone https://github.com/defunkt/coffee-mode

do you get an error or a warning?  I get a warning here with Git-2.39.2
from Debian stable.


        Stefan