Gentoo Archives: gentoo-portage-dev

From: Zac Medico <zmedico@g.o>
To: gentoo-portage-dev@l.g.o, "Michał Górny" <mgorny@g.o>, Alec Warner <antarus@g.o>
Subject: Re: [gentoo-portage-dev] [PATCH v2] misc: Distribute a repo.postsync.d hook to run gemato verification
Date: Wed, 17 Jan 2018 21:31:28
Message-Id: c3e58097-d449-fe23-e513-9042f0126990@gentoo.org
In Reply to: Re: [gentoo-portage-dev] [PATCH v2] misc: Distribute a repo.postsync.d hook to run gemato verification by "Michał Górny"
1 On 01/17/2018 01:09 PM, Michał Górny wrote:
2 > W dniu śro, 17.01.2018 o godzinie 12∶50 -0800, użytkownik Zac Medico
3 > napisał:
4 >>
5 >> The thing is, this pubring.gpg path tightly couples the hook to gentoo-keys.
6 >> I'd feel much more comfortable about including it with portage if we
7 >> used something like this command to query the pubring.gpg location:
8 >>
9 >> $ gkeys list-key -C gentoo -n snapshot
10 >>
11 >
12 > I suppose I can live with that. However, gkeys are quite a heavy
13 > dependency compared to the keyring, with the latter being the only real
14 > requirement for gemato. That is, if that gkeys function works out
15 > of the box for non-root users because I recall gkeys having that
16 > problem.
17
18 The above gkeys command works for me as any user. However, if I add
19 --keydir release to the arguments then it fails to return results unless
20 it's running as root. Do we need a working --keydir argument?
21 --
22 Thanks,
23 Zac

Attachments

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

Replies