Re: ELPA git repo contains zero-padded file modes and running ~$ make fails

[Stefan Kangas]

Stefan Monnier <monnier@iro.umontreal.ca> writes:

>>>>>>> I have this error when git-pulling the elpa repository:
>>>
>>>>>>>   guerry git/elpa ‹master› » git pull
>>>>>>>   remote: Counting objects: 64150, done.
>>>>>>>   remote: Compressing objects: 100% (22564/22564), done.
>>>>>>>   error: object 2699d230e3b592ae42506d7b5c969a7ac6a4593c:
>>>>>>> zeroPaddedFilemode: contains zero-padded file modes
>>>>>>>   fatal: erreur de fsck dans l'objet empaqueté
>>>>>>>   fatal: échec de index-pack
>>
>> Hmm... I thought I had fixed that.
>
> Actually, I had fixed that specific error over on `nongnu.git` (the error
> is a bad commit in `coffee-mode`).
> But indeed, `coffee-mode` used to live in `elpa.git` and there were
> left-over references to it so that error was still present on `elpa.git`.
> I believe I have fixed it now.
>
> [ The badDateOverflow problem on Embark is still with us, OTOH.  ]

As long as we keep them all in the repository, it's very likely that
we'll end up with bad commits in either GNU ELPA or NonGNU ELPA.

Is there something we could add to our scripts to avoid this from
happening in the future?  I'm thinking of adding a `git fsck` to our
scripts before pushing a branch to Savannah, or something.  Not sure
what's needed.