This is a tracking bug for things that needs to be resolved before gnupg 2.1 can be stabilized. As usual, please don't discuss in this report but file new bugs blocking this one.
For clarity, GnuPG 2.1 will not actually be stabilized. Once 2.1 reaches stable state upstream, gnupg 2.2 will be released, and this is the first candidate for stable in Gentoo as well. GnuPG 2.0 is EOL 2017
With the recent changes to 2.1.13, the 2.1 branch of gnupg is now ready to go stable dependent on the dependencies
Arches, please stabilize: =app-crypt/gnupg-2.1.15 Stable targets: alpha amd64
Including arm for stablereq as deps have been stabilized
Stable on alpha.
stable on amd64.
(In reply to Kristian Fiskerstrand from comment #1) > For clarity, GnuPG 2.1 will not actually be stabilized. Once 2.1 reaches > stable state upstream, gnupg 2.2 will be released, and this is the first > candidate for stable in Gentoo as well. GnuPG 2.0 is EOL 2017 (In reply to Kristian Fiskerstrand from comment #3) > Arches, please stabilize: > =app-crypt/gnupg-2.1.15 > Stable targets: alpha amd64 Could you make your mind up, please? You're also missing quite a few architectures here.
(In reply to Jeroen Roovers from comment #7) > (In reply to Kristian Fiskerstrand from comment #1) > > For clarity, GnuPG 2.1 will not actually be stabilized. Once 2.1 reaches > > stable state upstream, gnupg 2.2 will be released, and this is the first > > candidate for stable in Gentoo as well. GnuPG 2.0 is EOL 2017 > > (In reply to Kristian Fiskerstrand from comment #3) > > Arches, please stabilize: > > =app-crypt/gnupg-2.1.15 > > Stable targets: alpha amd64 > > Could you make your mind up, please? You're also missing quite a few > architectures here. "Make mind up"? Please..... I can't request stabilization for the other architectures before the dependency stabilization in the related bugs are fixed.
arm stable, all arches done.
Reopening to complete other arch when due
Arches, please stabilize: =app-crypt/gnupg-2.1.15 Stable targets: hppa ppc64
x86 stable
Dear Maintainer (or who is mainly involved in this stable request), This is an auto-generated message that will move the current component to the new component Stabilization. To ensure that the stabilization will proceed correctly, please fill the fields "Atoms to stabilize" and "Runtime testing required" as described here: https://archives.gentoo.org/gentoo-dev/message/4b2ef0e9aa7588224b8ae799c5fe31fa
Stable for HPPA.
ppc64 stable. Closing.
We need ia64, ppc, sparc for some reason were missing in CC.
(In reply to Alon Bar-Lev from comment #16) > We need ia64, ppc, sparc for some reason were missing in CC. GnuPG 1.4 will still be available in same slot that have these stable, I'm not convinced keeping stable support for two branches of gnupg is worthwhile on these architectures (in particular ia64 and sparc)
(In reply to Kristian Fiskerstrand from comment #17) > (In reply to Alon Bar-Lev from comment #16) > > We need ia64, ppc, sparc for some reason were missing in CC. > > GnuPG 1.4 will still be available in same slot that have these stable, I'm > not convinced keeping stable support for two branches of gnupg is worthwhile > on these architectures (in particular ia64 and sparc) This is a decision of archs, so far gnupg-2.0 was stabilize on these, if they would like top stop support we should make sure that all dependencies are also removed from these archs.
I was sure I added the arch at CC...
ppc stable
sparc stable
ia64 stable. Closing.
