Re: ELPA repository broken

[Stephen Leake <stephen_leake@stephe-leake.org>]

Andreas Schwab <schwab@linux-m68k.org> writes:

> Teemu Likonen <tlikonen@iki.fi> writes:
>
>> Stephen Leake [2016-02-15 11:33:20-06] wrote:
>>
>>> stephe@Takver4$ git clone git://git.sv.gnu.org/emacs/elpa
>>> Cloning into 'elpa'...
>>> remote: Counting objects: 93878, done.
>>> remote: Compressing objects: 100% (32515/32515), done.
>>> error: object 2699d230e3b592ae42506d7b5c969a7ac6a4593c:
>>> zeroPaddedFilemode: contains zero-padded file modes
>>> fatal: Error in object
>>>
>>> Can I fix this, or does some admin have to fix it?
>>
>> I think it's the same everywhere:
>>
>> $ git fsck
>>
>> Checking object directories: 100% (256/256), done.
>> warning in tree 2699d230e3b592ae42506d7b5c969a7ac6a4593c: contains
>> zero-padded file modes
>> Checking objects: 100% (93881/93881), done.
>
> This tree object is part of commit
> 2a59ce05bd0a86db1911f07adb942f10b8540614.  There is a quite similar
> commit 765c29826091b457b9b89daac52e4283b7294a40, which refers to tree
> d98e6fdf5b45326e1b7092757a7cf0f3684fb85d, the variant of the above
> without the zero padding.

Is there a bug that allowed the zero padding? The stackoverflow thread
did not answer that question.

If not, then fsckObjects = true should not abort a clone when it
detects such an object.

Or maybe that object is old, and the bug has since been fixed?

-- 
-- Stephe