From: "\"Paweł Hajdan, Jr.\"" <phajdan.jr@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] repoman commit unexpectedly drops FEATURES="sign" on error
Date: Wed, 19 Jun 2013 19:59:08 -0700 [thread overview]
Message-ID: <51C26FFC.1090000@gentoo.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 977 bytes --]
Today an interesting thing happened to my repoman, as I was committing a
change:
>>> Creating Manifest for /home/ph/gentoo-x86/dev-lang/v8
gpg: no default secret key: Unusable secret key
gpg: /home/ph/gentoo-x86/dev-lang/v8/Manifest: clearsign failed:
Unusable secret key
!!! !!! gpg exited with '2' status
!!! Disabled FEATURES='sign'
/var/cvsroot/gentoo-x86/dev-lang/v8/Manifest,v <-- Manifest
new revision: 1.321; previous revision: 1.320
Indeed my private key on that machine was expired:
pub 1024D/30427902 2009-08-05 [expired: 2013-06-10]
But after refreshing it (I have extended the expiration date) it is fine:
pub 1024D/30427902 2009-08-05 [expires: 2014-02-10]
I was surprised by repoman just dropping FEATURES="sign" . I'm aware
that at that time it has to commit an updated Manifest to prevent
breakages, so if gpg fails it proceeds, but is there something it could
do to check gpg sanity before committing anything?
Paweł
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 203 bytes --]
next reply other threads:[~2013-06-20 2:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-20 2:59 "Paweł Hajdan, Jr." [this message]
2013-06-20 3:25 ` [gentoo-dev] repoman commit unexpectedly drops FEATURES="sign" on error Zac Medico
2013-06-20 3:27 ` Zac Medico
2013-06-20 6:39 ` Michael Weber
2013-06-20 9:16 ` Michał Górny
2013-06-23 0:02 ` "Paweł Hajdan, Jr."
2013-06-23 8:19 ` Michał Górny
2013-06-23 21:06 ` Zac Medico
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=51C26FFC.1090000@gentoo.org \
--to=phajdan.jr@gentoo.org \
--cc=gentoo-dev@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