From: Vieri <rentorbuy@yahoo.com>
To: gentoo-proxy-maint@lists.gentoo.org
Subject: Re: [gentoo-proxy-maint] local branch gone
Date: Wed, 12 Dec 2018 15:53:40 +0000 (UTC) [thread overview]
Message-ID: <767057409.3358533.1544630020996@mail.yahoo.com> (raw)
In-Reply-To: <1544317926.3282851.1544623907665@mail.yahoo.com>
I now have this:
$ git pull --rebase gentoo master
remote: Enumerating objects: 1358, done.
remote: Counting objects: 100% (1358/1358), done.
remote: Compressing objects: 100% (90/90), done.
remote: Total 1816 (delta 1268), reused 1358 (delta 1268), pack-reused 458
Receiving objects: 100% (1816/1816), 674.35 KiB | 1.74 MiB/s, done.
Resolving deltas: 100% (1297/1297), completed with 491 local objects.
From https://github.com/gentoo/gentoo
* branch master -> FETCH_HEAD
775c75ac491..1eb533aad99 master -> gentoo/master
First, rewinding head to replay your work on top of it...
Applying: CATEGORY/PACKAGE: new ebuild / new package
error: gpg failed to sign the data
fatal: failed to write commit object
Seems good, except for that ugly fatal message. Should I worry about it?
Note that both gpg --version and gpg2 --version show the same version number (2.2.10).
Of course I defined:
$ git config --local user.signingkey 0xLONG-GPG-KEY
$ git config --local commit.gpgsign 1
$ git config --local push.gpgsign 1
I can see the key in .git/config, as well as with:
$ gpg --list-secret-keys --keyid-format LONG
Thanks,
Vieri
prev parent reply other threads:[~2018-12-12 15:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1959854123.3123203.1544601371408.ref@mail.yahoo.com>
2018-12-12 7:56 ` [gentoo-proxy-maint] local branch gone Vieri
2018-12-12 11:34 ` Corentin “Nado” Pazdera
2018-12-12 14:11 ` Vieri
2018-12-12 15:53 ` Vieri [this message]
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=767057409.3358533.1544630020996@mail.yahoo.com \
--to=rentorbuy@yahoo.com \
--cc=gentoo-proxy-maint@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox