As of today, I seem to be unable to a an "emerge --sync".
The process either hangs forever at the "Refreshing keys from keyserver step:
# emerge --sync
>>> Syncing repository 'gentoo' into '/usr/portage'...
* Using keys from /usr/share/openpgp-keys/gentoo-release.asc
* Refreshing keys from keyserver ...
Or, it fails because there are no public key to verify a manfest:
# emerge --sync
>>> Syncing repository 'gentoo' into '/usr/portage'...
* Using keys from /usr/share/openpgp-keys/gentoo-release.asc
* Refreshing keys from keyserver ...
[ ok ]
>>> Starting rsync with rsync://156.56.247.193/gentoo-portage...
[...]
receiving incremental file list
timestamp.chk
Number of files: 1 (reg: 1)
[...]
sent 109 bytes received 1.15K bytes 838.00 bytes/sec
total size is 32 speedup is 0.03
---------------------------------------------------------
[...]
receiving incremental file list
metadata/timestamp.chk
Number of files: 161,932 (reg: 134,486, dir: 27,446)
[...]
sent 27.56K bytes received 4.04M bytes 626.31K bytes/sec
total size is 218.65M speedup is 53.71
!!! Manifest verification failed:
OpenPGP verification failed:
gpg: Signature made Thu 05 Jul 2018 06:38:32 PM UTC
gpg: using RSA key E1D6ABB63BFCFB4BA02FDF1CEC590EEAC9189250
gpg: Can't check signature: No public key
q: Updating ebuild cache in /usr/portage ...
q: Finished 35635 entries in 0.141629 seconds
* IMPORTANT: config file '/etc/ssh/sshd_config' needs updating.
* See the CONFIGURATION FILES and CONFIGURATION FILES UPDATE TOOLS
* sections of the emerge man page to learn how to update config files.
Action: sync for repo: gentoo, returned code = 1
I've found all sorts of recipes to try to fix this for webrsync users
but I use plain-old "emerge --sync".
I also found a recipe that appears to recommend you completely wipe
portage and reinstall it from scratch using a snapshot. Is that
seriously what we're supposed to do?
--
Grant
