Gentoo Archives: gentoo-dev

From: Matthew Thode <prometheanfire@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] adding app-crypt/gentoo-keys to @system
Date: Wed, 20 Feb 2019 17:05:18
Message-Id: 20190220170507.ygs6sd33zymigvam@gentoo.org
In Reply to: Re: [gentoo-dev] adding app-crypt/gentoo-keys to @system by "Michał Górny"
1 On 19-02-20 08:35:10, Michał Górny wrote:
2 > On Tue, 2019-02-19 at 21:23 -0600, Matthew Thode wrote:
3 > > As the title says, I think this should be done.
4 > >
5 > > First sync is impossible to verify without keys (webrsync)
6 > > app-crypt/gentoo-keys has no dependencies, which help avoid some bloat
7 > > in the base install.
8 > >
9 >
10 > This is the wrong place to add it, and the wrong package.
11 >
12 > If Portage (still) needs it for whatever, then it should be a dependency
13 > of Portage.
14 >
15 > However, app-crypt/openpgp-keys-gentoo-release should be entirely
16 > sufficient, and it works without all the voodoo dependencies and 'run
17 > programs as root' logic of gkeys. If there's anything in Portage left
18 > not using it, it should be ported.
19 >
20
21 FEATURES="webrsync-gpg" emerge-webrsync fails to work with just the file.
22
23 PORTAGE_GPG_DIR="/var/lib/gentoo/gkeys/keyrings/gentoo/release" FEATURES="webrsync-gpg" emerge-webrsync
24 works
25
26 PORTAGE_GPG_DIR="/usr/share/openpgp-keys/" FEATURES="webrsync-gpg" emerge-webrsync
27 emerge-webrsync: error: signature verification failed
28 (same for the file).
29
30 Maybe some of the interior portage stuff should be fixed then?
31
32 --
33 Matthew Thode (prometheanfire)

Attachments

File name MIME type
signature.asc application/pgp-signature