Summary: | app-portage/gemato-15.2, 16.1 + portage-3.0.x failover from wkd to keyserver not working | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Hank Leininger <hlein> |
Component: | Stabilization | Assignee: | Michał Górny <mgorny> |
Status: | RESOLVED FIXED | ||
Severity: | normal | Keywords: | ALLARCHES, CC-ARCHES |
Priority: | Normal | Flags: | nattka:
sanity-check+
|
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: |
app-portage/gemato-16.2
|
Runtime testing required: | --- |
Description
Hank Leininger
2020-09-30 18:12:33 UTC
My bad. The code only accounts for non-200 status but I've completely forgotten to handle connect failures etc. The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=eeda16253769493db3bf50be19d7392302a5e89b commit eeda16253769493db3bf50be19d7392302a5e89b Author: Michał Górny <mgorny@gentoo.org> AuthorDate: 2020-10-01 12:17:09 +0000 Commit: Michał Górny <mgorny@gentoo.org> CommitDate: 2020-10-01 12:22:00 +0000 app-portage/gemato: Bump to 16.2 Bug: https://bugs.gentoo.org/745771 Signed-off-by: Michał Górny <mgorny@gentoo.org> app-portage/gemato/Manifest | 1 + app-portage/gemato/gemato-16.2.ebuild | 43 +++++++++++++++++++++++++++++++++++ 2 files changed, 44 insertions(+) Could you confirm that 16.2 solves your issue? If it does, I'll fast-stabilize it. Yes! Thanks @mgorny, with gemato-16.2 I once again get the expected behavior:
# equery l gemato portage
* Searching for gemato ...
[I-O] [ ] app-portage/gemato-16.2:0
* Searching for portage ...
[IP-] [ ] sys-apps/portage-3.0.8:0
# emerge --sync
>>> 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 ... [ ok ]
Fetching most recent snapshot ...
[snip]
Arch teams, please fast-stabilize this version. amd64 arm arm64 hppa ppc ppc64 sparc x86 (ALLARCHES) done all arches done |