unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Manuel Uberti <manuel.uberti@inventati.org>
Cc: 65241@debbugs.gnu.org
Subject: bug#65241: 30.0.50; Cannot clone NonGNU ELPA
Date: Sat, 12 Aug 2023 09:03:39 +0200	[thread overview]
Message-ID: <87h6p4spx0.fsf@gmx.de> (raw)
In-Reply-To: <63634a04-ab14-0d3c-e9cb-b810e9ee7d10@inventati.org> (Manuel Uberti's message of "Sat, 12 Aug 2023 08:57:24 +0200")

Manuel Uberti <manuel.uberti@inventati.org> writes:

> Hi Michael

Hi Manuel,

>> Try
>> --8<---------------cut here---------------start------------->8---
>> # git config --global transfer.fsckObjects false
>> --8<---------------cut here---------------end--------------->8---
>
> Thanks, changing transfer.fsckObjects makes it work. Is it really a
> problem with my Git configuration, though?

No. IIRC, there are commits in ELPA which have zero-padded file
modes. It doesn't seem to be trivial to fix it in the git repo, and so
we need this change. This was discussed somewhere in the mailing lists,
but I have no reference.

I don't know git sufficiently to know, whether this setting could be
restricted just to the elpa repos. But at least it should be added to
the respective README and README.org of the repositories.

Best regards, Michael.





  reply	other threads:[~2023-08-12  7:03 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 [this message]
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
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=87h6p4spx0.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=65241@debbugs.gnu.org \
    --cc=manuel.uberti@inventati.org \
    /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).