Created attachment 585964 [details] Output of emerge --info When running emerge --sync using a kernel with ipv6 disabled, ot hangs at the refreshing keys stage. This is the messages I get: >>> Syncing repository 'gentoo' into '/usr/portage'... * Using keys from /usr/share/openpgp-keys/gentoo-release.asc * Refreshing keys via WKD ... [ !! ] * Refreshing keys from keyserver hkps://keys.gentoo.org ...OpenPGP keyring refresh failed: gpg: refreshing 4 keys from hkps://keys.gentoo.org gpg: keyserver refresh failed: No keyserver available After that, it tries again multiple times, each time repeating the last two lines, before giving up and exiting. Using a kernel with ipv6 enabled, emerge --sync completes successfully. I started experiencing this problem when the line sync-openpgp-keyserver = hkps://keys.gentoo.org was added in /usr/share/portage/config/repos.conf (i believe with portage-2.3.69): without this line, emerge is able to sync successfully even without ipv6. I already saw bug #646194 (actually, it's what suggested me to try enabling ipv6 in the kernel in the first place), but as it's supposed to be fixed, I decided to create another one.
I confirm that's bug present in Raspberry pi 3 and generic Gentoo PC. pi64 ~ # LC_ALL=C eix-sync * Running emerge --sync >>> Syncing repository 'gentoo' into '/var/db/repos/gentoo'... * Using keys from /usr/share/openpgp-keys/gentoo-release.asc * Refreshing keys via WKD ... [ !! ] * Refreshing keys from keyserver hkps://keys.gentoo.org ...OpenPGP keyring refresh failed: gpg: refreshing 4 keys from hkps://keys.gentoo.org gpg: keyserver refresh failed: Server indicated a failure OpenPGP keyring refresh failed: gpg: refreshing 4 keys from hkps://keys.gentoo.org gpg: keyserver refresh failed: Server indicated a failure ^C Exiting on signal Signals.SIGINT * Time statistics: 26 seconds total
I vote for this bug should be solved.
And I confirm that issue starts when I switched to router that doesn't support ipv6 yet.
Maybe the same or related to bug 704456.
=app-crypt/gnupg-2.2.19 solves the issue
1. Update portage tree via emerge-webrsync 2. Install =app-crypt/gnupg-2.2.19 with ~ keyword
That bug seems to be fixed.
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/proj/portage.git/commit/?id=9268a92b9666eaaf263999b18220c0d56d8c476c commit 9268a92b9666eaaf263999b18220c0d56d8c476c Author: Sam James <sam@gentoo.org> AuthorDate: 2023-08-13 04:36:04 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2023-08-17 06:52:55 +0000 sync: rsync, git: respect --debug for gemato Respect --debug and pass it down to gemato so we get nice debugging output when e.g. 'refreshing keys' is stuck. Bug: https://bugs.gentoo.org/646194 Bug: https://bugs.gentoo.org/647696 Bug: https://bugs.gentoo.org/691666 Bug: https://bugs.gentoo.org/779766 Bug: https://bugs.gentoo.org/873133 Bug: https://bugs.gentoo.org/906875 Bug: https://github.com/projg2/gemato/issues/7 Bug: https://github.com/projg2/gemato/issues/25 Signed-off-by: Sam James <sam@gentoo.org> lib/portage/sync/modules/git/git.py | 15 +++++++++++++-- lib/portage/sync/modules/rsync/rsync.py | 11 +++++++++-- lib/portage/sync/syncbase.py | 12 ++++++++---- 3 files changed, 30 insertions(+), 8 deletions(-)
