| 1 |
2018-07-04 21:01 GMT+03:00 Mick <michaelkintzios@×××××.com>: |
| 2 |
> On Wednesday, 4 July 2018 18:57:56 BST gevisz wrote: |
| 3 |
>> 2018-07-04 11:55 GMT+03:00 Alex Thorne <lexiconifernelius@×××××.com>: |
| 4 |
>> >> I use rsync and get the following for more than a day now; |
| 5 |
>> >> |
| 6 |
>> >> !!! Manifest verification failed: |
| 7 |
>> >> OpenPGP verification failed: |
| 8 |
>> >> gpg: Signature made Wed 04 Jul 2018 04:08:28 AM UTC |
| 9 |
>> >> gpg: using RSA key |
| 10 |
>> >> E1D6ABB63BFCFB4BA02FDF1CEC590EEAC9189250 |
| 11 |
>> >> gpg: Can't check signature: No public key |
| 12 |
>> > |
| 13 |
>> > I'm seeing this too. For me `app-crypt/gentoo-keys` is somehow no longer |
| 14 |
>> > installed and `/var/lib/gentoo/gkeys` is missing. I have no idea how this |
| 15 |
>> > happened. Perhaps it somehow got into `emerge --depclean` and I didn't |
| 16 |
>> > catch it. |
| 17 |
>> |
| 18 |
>> No. Gentoo maintainers just overlooked that all Gentoo signing keys expired |
| 19 |
>> on July 1, and added new openpgp-keys-gentoo into portage tree only on July |
| 20 |
>> 2. |
| 21 |
>> |
| 22 |
>> So, since July 1, rsync cannot verify any new portage tree and cannot |
| 23 |
>> download app-crypt/openpgp-keys-gentoo-release-20180702 |
| 24 |
>> |
| 25 |
>> It was discovered in the thread |
| 26 |
>> "All Gentoo signing key expired and no way to fix it" |
| 27 |
> |
| 28 |
> Is there a documented manual workaround we could follow at present, |
| 29 |
> irrespective of our sync'ing mechanism of choice? |
| 30 |
|
| 31 |
For me, it somehow worked by manually refreshing the Gentoo signing keys by |
| 32 |
executing the following two commands: |
| 33 |
# gpg --homedir /var/lib/gentoo/gkeys/keyrings/gentoo/release --refresh-keys |
| 34 |
# gpg --keyserver hkps.pool.sks-keyservers.net --recv-keys 0xDB6B8C1F96D8BF6D |
| 35 |
in different order and sourcing /etc/profile |
| 36 |
|
| 37 |
But, please, note that I use emerge-webrsync to update the portage tree. |
Archives