From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: phajdan.jr@gentoo.org
Subject: Re: [gentoo-dev] repoman commit unexpectedly drops FEATURES="sign" on error
Date: Thu, 20 Jun 2013 11:16:46 +0200 [thread overview]
Message-ID: <20130620111646.4ecb37d4@gentoo.org> (raw)
In-Reply-To: <51C26FFC.1090000@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 794 bytes --]
Dnia 2013-06-19, o godz. 19:59:08
""Paweł Hajdan, Jr."" <phajdan.jr@gentoo.org> napisał(a):
> 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?
I'm pretty sure this was discussed already, either here or on bugzie.
Doing test signatures won't cover all failures.
IMHO the best thing to do would be to drop CVS keywords and let repoman
do normal commits instead of this two-step thing. But some of the devs
really prefer to keep them, at least until we migrate to git and have
better ways of e.g. checking the file version.
--
Best regards,
Michał Górny
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 966 bytes --]
next prev parent reply other threads:[~2013-06-20 9:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-20 2:59 [gentoo-dev] repoman commit unexpectedly drops FEATURES="sign" on error "Paweł Hajdan, Jr."
2013-06-20 3:25 ` Zac Medico
2013-06-20 3:27 ` Zac Medico
2013-06-20 6:39 ` Michael Weber
2013-06-20 9:16 ` Michał Górny [this message]
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=20130620111646.4ecb37d4@gentoo.org \
--to=mgorny@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=phajdan.jr@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