| 1 |
On 01/17/2018 01:31 PM, Zac Medico wrote: |
| 2 |
> On 01/17/2018 01:09 PM, Michał Górny wrote: |
| 3 |
>> W dniu śro, 17.01.2018 o godzinie 12∶50 -0800, użytkownik Zac Medico |
| 4 |
>> napisał: |
| 5 |
>>> |
| 6 |
>>> The thing is, this pubring.gpg path tightly couples the hook to gentoo-keys. |
| 7 |
>>> I'd feel much more comfortable about including it with portage if we |
| 8 |
>>> used something like this command to query the pubring.gpg location: |
| 9 |
>>> |
| 10 |
>>> $ gkeys list-key -C gentoo -n snapshot |
| 11 |
>>> |
| 12 |
>> |
| 13 |
>> I suppose I can live with that. However, gkeys are quite a heavy |
| 14 |
>> dependency compared to the keyring, with the latter being the only real |
| 15 |
>> requirement for gemato. That is, if that gkeys function works out |
| 16 |
>> of the box for non-root users because I recall gkeys having that |
| 17 |
>> problem. |
| 18 |
> |
| 19 |
> The above gkeys command works for me as any user. However, if I add |
| 20 |
> --keydir release to the arguments then it fails to return results unless |
| 21 |
> it's running as root. Do we need a working --keydir argument? |
| 22 |
|
| 23 |
I've posted a fix here: https://bugs.gentoo.org/644906 |
| 24 |
-- |
| 25 |
Thanks, |
| 26 |
Zac |
Archives