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: Wed, 06 Sep 2023 07:49:42 -0400 [thread overview]
Message-ID: <jwvsf7rh6ij.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <CADwFkmmm9_zT7kqY-nV19Oygcj_cxM7pUhQ7s64LCMpLdTOc4Q@mail.gmail.com> (Stefan Kangas's message of "Tue, 5 Sep 2023 16:25:05 -0700")
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
next prev parent reply other threads:[~2023-09-06 11:49 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvsf7rh6ij.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.