From: Matthew Carter <m@ahungry.com>
To: Jackson Hamilton <jackson@jacksonrayhamilton.com>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>,
emacs-devel <emacs-devel@gnu.org>
Subject: Re: Requesting review before pushing patch to ELPA
Date: Thu, 05 Feb 2015 13:39:05 -0500 [thread overview]
Message-ID: <87iofgdwza.fsf@ahungry.com> (raw)
In-Reply-To: <CAGiE8AyrXq9NfP13g-ksb1d-NGJDmADHgf1ve_sxUzeLhvU7yQ@mail.gmail.com> (Jackson Hamilton's message of "Thu, 5 Feb 2015 10:17:57 -0800")
Jackson Hamilton <jackson@jacksonrayhamilton.com> writes:
> Heys guys, I am having an issue pushing to ELPA:
>
> $ git push origin master
> Counting objects: 1127, done.
> Delta compression using up to 4 threads.
> Compressing objects: 100% (431/431), done.
> fatal: read error: Connection reset by peer
> error: pack-objects died of signal 13
> error: failed to push some refs to 'git://git.sv.gnu.org/emacs/elpa'
>
> I am not sure what's up.
>
> I looked up these errors, and apparently "error: pack-objects died of
> signal 13" has something to do with the size of the push? The push does
> include my whole project history, but I don't have any particularly large
> binary files in my repo besides maybe 6 or 7 .png files.
>
> I've added the "Project Members GPG Keyring" with gpg --import. Perhaps I
> am still not properly authenticated? (Sorry, I'm not too familiar with gpg
> or keys.)
>
> Thanks,
> Jackson
>
> On Thu, Feb 5, 2015 at 6:10 AM, Stefan Monnier <monnier@iro.umontreal.ca>
> wrote:
>
Hi Jackson,
When you issue 'git remote -v' do you see something similar to:
origin jackson@git.sv.gnu.org:/srv/git/emacs/elpa.git
Or do you see an URL without your Savannah username included?
The default checkout didn't seem pushable to me (I had your same issue).
I fixed by setting the remote to what you see above (well, in my case I
just re-cloned via):
git clone 'jackson@git.sv.gnu.org:/srv/git/emacs/elpa.git'
Obviously make sure to add your SSH keys to Savannah first (and in the
sample commands change 'jackson' to your Savannah user').
--
Matthew Carter (m@ahungry.com)
http://ahungry.com
next prev parent reply other threads:[~2015-02-05 18:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-02 7:49 Requesting review before pushing patch to ELPA Jackson Hamilton
2015-02-02 17:58 ` Stefan Monnier
2015-02-03 5:57 ` Jackson Hamilton
2015-02-03 12:13 ` Artur Malabarba
2015-02-04 9:24 ` Jackson Hamilton
2015-02-04 11:15 ` Artur Malabarba
2015-02-04 11:16 ` Artur Malabarba
2015-02-03 17:51 ` Stefan Monnier
2015-02-04 9:32 ` Jackson Hamilton
2015-02-04 15:14 ` Stefan Monnier
2015-02-04 19:46 ` Jackson Hamilton
2015-02-04 19:48 ` Dmitry Gutov
2015-02-04 21:58 ` Stefan Monnier
2015-02-05 8:05 ` Jackson Hamilton
2015-02-05 14:10 ` Stefan Monnier
2015-02-05 18:17 ` Jackson Hamilton
2015-02-05 18:39 ` Matthew Carter [this message]
2015-02-05 18:48 ` Jackson Hamilton
2015-02-05 20:22 ` Stefan Monnier
2015-02-04 15:13 ` Stefan Monnier
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=87iofgdwza.fsf@ahungry.com \
--to=m@ahungry.com \
--cc=emacs-devel@gnu.org \
--cc=jackson@jacksonrayhamilton.com \
--cc=monnier@iro.umontreal.ca \
/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).