> We should look out for potential regressions when connecting to servers with exclusive IPv4 or IPv6 connectivity, to make sure the server is not getting marked as 'dead' due to missing one of the versions.
+1. Please do this during SRU verification, as well as checking that dual stack works as expected. I accept though that the code path being added is only when errno == EAFNOSUPPORT so scope for regression is very limited. The Hirsute release pocket currently has 2.2.20-1ubuntu1, same as Groovy. So I can't accept 2.2.20-1ubuntu1 into Groovy, since then the Hirsute release pocket would be a lower version than what is in Groovy. I suggest you use 2.2.20-1ubuntu1.20.10.1 based on https://wiki.ubuntu.com/SecurityTeam/UpdatePreparation#Update_the_packaging. Alternatively this problem will be resolved as soon as 2.2.20-1ubuntu2 in hirsute-proposed migrates. Please fix the Groovy upload, or otherwise ping when fixed. I see no reason to block right now on accepting the Focal upload, but it would be nice to get both into proposed and then released at once, so users don't regress when upgrading from Focal to Groovy. ** Changed in: gnupg2 (Ubuntu Focal) Status: In Progress => Fix Committed ** Changed in: gnupg2 (Ubuntu Groovy) Status: In Progress => Incomplete ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1910432 Title: dirmngr doesn't work with kernel parameter ipv6.disable=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnupg2/+bug/1910432/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
