From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: Manuel Uberti <manuel.uberti@inventati.org>, 65241@debbugs.gnu.org
Subject: bug#65241: 30.0.50; Cannot clone NonGNU ELPA
Date: Fri, 01 Sep 2023 17:21:32 -0400 [thread overview]
Message-ID: <jwvcyz1k39l.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <CADwFkm=H6M4qDRgcXkf7WePJhsT=mCxXZ_P7eJ_6x747kMKAAA@mail.gmail.com> (Stefan Kangas's message of "Fri, 1 Sep 2023 22:27:13 +0200")
>> $ git clone git://git.savannah.gnu.org/emacs/nongnu.git
>> Cloning into 'nongnu'...
>> remote: Counting objects: 425227, done.
>> remote: Compressing objects: 100% (145570/145570), done.
>> error: object 2699d230e3b592ae42506d7b5c969a7ac6a4593c:
>> zeroPaddedFilemode: contains zero-padded file modes
>> fatal: fsck error in packed object
>> fatal: fetch-pack: invalid index-pack output
>
> I thought we fixed that, but maybe that was only for GNU ELPA?
Indeed we had such a problem over in `elpa.git` and we solved it, but
that problem can re-appear any time we pull from some (old(enough))
upstream repository.
> Stefan M, do you have any comments? Is there anything we could do here?
`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.
Stefan
next prev parent reply other threads:[~2023-09-01 21:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-12 6:01 bug#65241: 30.0.50; Cannot clone NonGNU ELPA Manuel Uberti via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-12 6:13 ` Corwin Brust
2023-08-12 6:17 ` Manuel Uberti via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-12 6:46 ` Andreas Schwab
2023-08-12 6:54 ` Michael Albinus
2023-08-12 6:57 ` Manuel Uberti via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-12 7:03 ` Michael Albinus
2023-08-12 7:04 ` Manuel Uberti via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-01 20:27 ` Stefan Kangas
2023-09-01 21:21 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-09-05 23:25 ` Stefan Kangas
2023-09-06 11:49 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-06 12:03 ` Stefan Kangas
2023-09-06 15:32 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-06 16:05 ` Stefan Kangas
2023-09-06 21:01 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-06 21:10 ` Stefan Kangas
2023-09-06 23:14 ` Corwin Brust
2023-09-08 10:59 ` Stefan Kangas
2023-09-08 16:14 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-08 16:23 ` Stefan Kangas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvcyz1k39l.fsf-monnier+emacs@gnu.org \
--to=bug-gnu-emacs@gnu.org \
--cc=65241@debbugs.gnu.org \
--cc=manuel.uberti@inventati.org \
--cc=monnier@iro.umontreal.ca \
--cc=stefankangas@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).