ELPA repository broken

ELPA repository broken

[Stephen Leake]

I'm upgrading to a new computer (Windows 8.1), so I'm checking out Gnu
ELPA again.

I have two issues:

1) using git clone git://git.sv.gnu.org/emacs/elpa works until it
encounters an error:

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?


2) using ssh (for write access) gives a different error:

git clone ssh://stephen_leake@git.sv.gnu.org/emacs/elpa
Cloning into 'elpa'...
fatal: '/emacs/elpa' does not appear to be a git repository
fatal: Could not read from remote repository.


I obtained this URL by replacing "git://" with "ssh://stephen_leake";
the same transformation on the emacs git URL works fine.

What is the proper ssh URL syntax for Gnu ELPA?

-- 
-- Stephe

Re: ELPA repository broken

[Michael Heerdegen]

Stephen Leake <stephen_leake@stephe-leake.org> writes:

> 1) using git clone git://git.sv.gnu.org/emacs/elpa works until it
> encounters an error:

Seems to work here without error.


Michael.

Re: ELPA repository broken

[Stephen Leake]

Michael Heerdegen <michael_heerdegen@web.de> writes:

> Stephen Leake <stephen_leake@stephe-leake.org> writes:
>
>> 1) using git clone git://git.sv.gnu.org/emacs/elpa works until it
>> encounters an error:
>
> Seems to work here without error.

I'm using Cygwin git 2.7.0.

Ah; I recently added "fsckObjects = true" to ~/.gitconfig; commenting
that out lets the checkout succeed.

So there is an error in the repository, but most users are ignoring it.

There must be a way to fix the error.

-- 
-- Stephe

Re: ELPA repository broken

[Andreas Schwab]

Stephen Leake <stephen_leake@stephe-leake.org> writes:

> I obtained this URL by replacing "git://" with "ssh://stephen_leake";
> the same transformation on the emacs git URL works fine.

Does it?

$ git ls-remote ssh://git.sv.gnu.org/emacs
fatal: '/emacs' does not appear to be a git repository
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
$ git ls-remote ssh://git.sv.gnu.org/srv/git/emacs
ab7583a2b00d13207ab1c325c25c520a33859eee        HEAD
[...]

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

Re: ELPA repository broken

[Stephen Leake]

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

> Stephen Leake <stephen_leake@stephe-leake.org> writes:
>
>> I obtained this URL by replacing "git://" with "ssh://stephen_leake";
>> the same transformation on the emacs git URL works fine.
>
> Does it?

The Savannah Emacs summary page gives these two git URLs:

Emacs: git clone -b master git://git.sv.gnu.org/emacs.git

ELPA: git clone git://git.sv.gnu.org/emacs/elpa

Replacing "git://" with "ssh://stephen_leake@" (I left out the @ above)
gives:

Emacs: git clone -b master ssh://stephen_leake@git.sv.gnu.org/emacs.git

ELPA: git clone ssh://stephen_leake@git.sv.gnu.org/emacs/elpa


Hmm. The Emacs URL worked for me last week when I checked out Emacs;
it's in emacs/master/.git/config. Now it's not working with "git clone";
same error as ELPA. But "git fetch" works in that workspace. Sigh.

-- 
-- Stephe

Re: ELPA repository broken

[Andreas Schwab]

Stephen Leake <stephen_leake@stephe-leake.org> writes:

> Hmm. The Emacs URL worked for me last week when I checked out Emacs;
> it's in emacs/master/.git/config. Now it's not working with "git clone";
> same error as ELPA. But "git fetch" works in that workspace. Sigh.

What matters is what git remote -v tells you.

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

Re: ELPA repository broken

[Stephen Leake]

Stephen Leake <stephen_leake@stephe-leake.org> writes:

> Andreas Schwab <schwab@linux-m68k.org> writes:
>
>> Stephen Leake <stephen_leake@stephe-leake.org> writes:
>>
>>> I obtained this URL by replacing "git://" with "ssh://stephen_leake";
>>> the same transformation on the emacs git URL works fine.
>>
>> Does it?
>
> The Savannah Emacs summary page gives these two git URLs:
>
> Emacs: git clone -b master git://git.sv.gnu.org/emacs.git
>
> ELPA: git clone git://git.sv.gnu.org/emacs/elpa
>
> Replacing "git://" with "ssh://stephen_leake@" (I left out the @ above)
> gives:
>
> Emacs: git clone -b master ssh://stephen_leake@git.sv.gnu.org/emacs.git
>
> ELPA: git clone ssh://stephen_leake@git.sv.gnu.org/emacs/elpa
>
>
> Hmm. The Emacs URL worked for me last week when I checked out Emacs;
> it's in emacs/master/.git/config. Now it's not working with "git clone";
> same error as ELPA. But "git fetch" works in that workspace. Sigh.

I take it back; I did not compare the URLs carefully. Here's what works
via ssh:

ssh://stephen_leake@git.sv.gnu.org:/srv/git/emacs/elpa.git

note the ":/srv/git" and the ".git".

-- 
-- Stephe

Re: ELPA repository broken

[Alain Schneble]

Stephen Leake <stephen_leake@stephe-leake.org> writes:

> I'm upgrading to a new computer (Windows 8.1), so I'm checking out Gnu
> ELPA again.
>
> I have two issues:
>
> 1) using git clone git://git.sv.gnu.org/emacs/elpa works until it
> encounters an error:
>
> 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

I just tried it out on a Windows 10 machine with git version
2.6.2.windows.1.  Seems to work properly here as well.  I got no error
with the very same repository URL.

Re: ELPA repository broken

[Alain Schneble]

Alain Schneble <a.s@realize.ch> writes:

> Stephen Leake <stephen_leake@stephe-leake.org> writes:
>
>> I'm upgrading to a new computer (Windows 8.1), so I'm checking out Gnu
>> ELPA again.
>>
>> I have two issues:
>>
>> 1) using git clone git://git.sv.gnu.org/emacs/elpa works until it
>> encounters an error:
>>
>> 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
>
> I just tried it out on a Windows 10 machine with git version
> 2.6.2.windows.1.  Seems to work properly here as well.  I got no error
> with the very same repository URL.

...and I get the same error with fsckObjects set to true now as well.  :(

Re: ELPA repository broken

[Teemu Likonen]

[-- Attachment #1: Type: text/plain, Size: 965 bytes --]

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.


Here's some interesting discussion:

http://stackoverflow.com/questions/15598465/should-i-worry-about-git-fsck-warning-contains-zero-padded-file-modes

-- 
/// Teemu Likonen   - .-..   <https://github.com/tlikonen> //
// PGP: 4E10 55DC 84E9 DFF6 13D7 8557 719D 69D3 2453 9450 ///

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]

Re: ELPA repository broken

[Stephen Leake]

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

The git-fsck man page says that _checks_ for errors; it does _not_ say
it _fixes_ the errors.

-- 
-- Stephe

Re: ELPA repository broken

[Andreas Schwab]

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.

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

Re: ELPA repository broken

[Stephen Leake]

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

Re: ELPA repository broken

[Paul Eggert]

I filed this as Bug#22690, here:

http://bugs.gnu.org/22690

I assume a Savannah sysadmin will need to fix it.

Re: ELPA repository broken

[Andreas Schwab]

Paul Eggert <eggert@cs.ucla.edu> writes:

> I assume a Savannah sysadmin will need to fix it.

There is nothing you can do about it.  It is cast in stone.

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

Re: ELPA repository broken

[Paul Eggert]

Andreas Schwab wrote:
> There is nothing you can do about it.  It is cast in stone.

There's always *something* we can do about it. We could ask ESR to convert the 
ELPA repository from git to bzr format. (I'd love to see the expression on his 
face! :-)

Less drastically, a Savannah sysadmin could do a fast-export followed by a 
fast-import. Then developers can clone the cleaned-up repository instead. We 
could keep the old repository available read-only for a while, for convenience 
in analyzing old developer clones. Admittedly this is not something one should 
do casually, but really, developing with a corrupt repository is not a good way 
to go.

Re: ELPA repository broken

[Andreas Schwab]

Paul Eggert <eggert@cs.ucla.edu> writes:

> developing with a corrupt repository is not a good way to go.

It's not currupt, just non-canonical.

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

Re: ELPA repository broken

[Paul Eggert]

On 02/16/2016 12:49 AM, Andreas Schwab wrote:
> It's not corrupt, just non-canonical.

True, I should have used a more-accurate adjective. Still, the 
repository is likely to confuse people into avoiding fsckObjects, or at 
least to make Emacs development tricker to set up. So it's broken and 
should get fixed.