On 10/17/2012 12:16 AM, Michał Górny wrote: > On Tue, 16 Oct 2012 22:54:04 +0000 > "Robin H. Johnson" <robb...@gentoo.org> wrote: >> As such, we've decided to make the PORTAGE_GPG_KEY strictly enforce what >> was originally intended. >> >> - You must specify a key or subkey exactly. >> - The leading "0x" is optional. >> - If you want to use a subkey, per the PGP specifications, you must >> suffix your keyid with "!". >> - Your keyid is exactly: 8, 16, 24, 32 xor 40 hexdigits long. > > Isn't that fixing the issue from the wrong end? > > I agree that the keyids in commit messages should follow some kind > of spec. But I rather think that portage should be modified to convert > any supported argument to follow that spec rather than the spec being > forced into the configuration file.
If you file a bug and tell me what gpg commands to run, then I'll add it to repoman. > Also, will that matter anymore after the git conversion? The repoman PORTAGE_GPG_KEY validation is only triggered if layout.conf does not specify "sign-manifests = false": http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=d40c242a4c9a9b666fd8730734b149bce2dd7cd9 -- Thanks, Zac
