Summary: | app-crypt/gnupg-2.4.4-r1: stablereq | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Michał Górny <mgorny> |
Component: | Stabilization | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | RESOLVED FIXED | ||
Severity: | enhancement | CC: | base-system, pacho |
Priority: | Normal | Keywords: | CC-ARCHES, PullRequest |
Version: | unspecified | Flags: | nattka:
sanity-check+
|
Hardware: | All | ||
OS: | Linux | ||
See Also: | https://github.com/gentoo/gentoo/pull/35368 | ||
Whiteboard: | |||
Package list: |
app-crypt/gnupg-2.4.4-r1
|
Runtime testing required: | --- |
Bug Depends on: | 899306 | ||
Bug Blocks: | 924386 |
Description
Michał Górny
2022-03-24 18:16:17 UTC
Unable to check for sanity:
> no match for package: app-crypt/gnupg-2.3.4-r2
Unable to check for sanity:
> no match for package: app-crypt/gnupg-2.3.4-r3
Maybe it makes sense to stabilize dev-libs/libgcrypt-1.10.1 here too? (Both have been in-tree for 47 days now) (In reply to Matt Turner from comment #3) > Maybe it makes sense to stabilize dev-libs/libgcrypt-1.10.1 here too? (Both > have been in-tree for 47 days now) Good idea! Unable to check for sanity:
> no match for package: dev-libs/libgcrypt-1.10.1-r1
Unable to check for sanity:
> no match for package: app-crypt/gnupg-2.3.6-r1
Unable to check for sanity:
> no match for package: app-crypt/gnupg-2.3.7-r1
I suspect we want to move to gnupg-2.3.8 and depend on bug 899306 All sanity-check issues have been resolved Unable to check for sanity:
> no match for package: app-crypt/gnupg-2.3.8
All sanity-check issues have been resolved Unable to check for sanity:
> no match for package: app-crypt/gnupg-2.4.3
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=45ed86aa273d9bb10f4856de72616d889f43f016 commit 45ed86aa273d9bb10f4856de72616d889f43f016 Author: Hank Leininger <hlein@korelogic.com> AuthorDate: 2024-02-16 04:29:49 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2024-02-18 10:12:32 +0000 app-crypt/gnupg: fix dirmngr behind a proxy Adapted from upstream patches: https://dev.gnupg.org/rG04cbc3074aa98660b513a80f623a7e9f0702c7c9 https://dev.gnupg.org/rG848546b05ab0ff6abd47724ecfab73bf32dd4c01 Signed-off-by: Hank Leininger <hlein@korelogic.com> Closes: https://bugs.gentoo.org/924606 Bug: https://bugs.gentoo.org/835949 Closes: https://github.com/gentoo/gentoo/pull/35368 Signed-off-by: Sam James <sam@gentoo.org> .../gnupg/files/gnupg-2.4.4-dirmngr-proxy.patch | 91 ++++++++++ app-crypt/gnupg/gnupg-2.4.4-r1.ebuild | 197 +++++++++++++++++++++ 2 files changed, 288 insertions(+) Upstream consider 2.2.x legacy at this point (although still supported) so let's go ahead. ppc64 done amd64 done x86 done arm done sparc done ppc done arm64 done hppa done all arches done |