unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "N. Jackson" <nljlistbox2@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: Failure trying to clone Elpa
Date: Sun, 29 Jul 2018 17:03:56 -0400	[thread overview]
Message-ID: <877eldpxdv.fsf@moondust.localdomain> (raw)
In-Reply-To: CAM-tV-_wqmMn8UXhodFQSJzWdJLB6-oPPG0yvZC5ma082cvWMA@mail.gmail.com

Thanks Noam,

At 13:31 -0400 on Sunday 2018-07-29, Noam Postavsky wrote:
>
> It's a known problem in the Elpa repository, if you have enabled
> transfer.fsckObjects in your git config, then you have to disable it
> to clone.
>
> See https://debbugs.gnu.org/cgi/bugreport.cgi?bug=22690

I was going to say that I have no git configuration but it turns
out that I do. In addition to my name I have:

  [transfer]
          fsckObjects = true
  [fetch]
          fsckObjects = true
  [receive]
          fsckObjects = true

I read the bug report and the man page for `git clone' and then
cast around more generally in the git documentation but after an
hour or so I failed to find a way to turn off individual options
on the git command line and I failed to find a way to tell git to
ignore configuration files.

In the end, I went with the crude:

$ mv ~/.gitconfig ~/.gitconfig.no; \
  git clone git://git.sv.gnu.org/emacs/elpa; \
  mv ~/.gitconfig.no ~/.gitconfig

In any case, I think that https://savannah.gnu.org/projects/emacs
should say that the emacs/elpa repository is corrupt and will fail
`git-fsck' near where it gives the command to clone the repository.





  reply	other threads:[~2018-07-29 21:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-29 17:26 Failure trying to clone Elpa N. Jackson
2018-07-29 17:31 ` Noam Postavsky
2018-07-29 21:03   ` N. Jackson [this message]
2018-07-29 21:28     ` Andreas Schwab

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=877eldpxdv.fsf@moondust.localdomain \
    --to=nljlistbox2@gmail.com \
    --cc=emacs-devel@gnu.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).