10:43 < zmedico> 2.1.10.40 is the current stable candidate 10:43 < darkside_> the releng team can't just cordinate workarounds very easily. much easier to get the tree fixed 10:45 < zmedico> anyways, can stabilize 2.1.10.40 in about a week or so We need .40 stabilized ASAP for three reasons 1) stage building is failing due to ca-certs, 2) user are hitting ca-certs issue in the wild (same underlying issue as #1), 3) thin manifests are popular. Please accelerate the stablereq timeline for #1.
I've just learned that .40 has quiet-build=y by default and council doesn't allow this... or something. We need a fast resolution here.
(In reply to comment #1) > I've just learned that .40 has quiet-build=y by default and council doesn't > allow this... or something. We need a fast resolution here. I'm doing a 2.1.10.41 release today with --quiet-build disabled by default (see bug 390523).
So, with my releng hat on, let's ask the arch teams to stabilize this version ASAP.
arch teams: The sys-apps/portage-2.1.10.41 release has only been in the tree for 4 days now, but I think it's perfectly safe to stabilize it now. Bug 381649 tracks bugs fixed since 2.1.10.11. Also, here's a note from RELEASE-NOTES: * FEATURES=fixpackages is now enabled unconditionally. Set --package-moves=n in EMERGE_DEFAULT_OPTS if you need to temporarily avoid package moves for some reason.
Archtested on x86: All tests passed, did some test emerges with various switches, everything seems fine
(In reply to comment #5) > Archtested on x86: All tests passed, did some test emerges with various > switches, everything seems fine +1 on amd64
x86/amd64 stable, thanks JD
Stable for HPPA.
arm stable
alpha stable.
ia64/m68k/s390/sh/sparc stable wrt #394695
ppc done
Superseded by bug 400559.
*** Bug 401727 has been marked as a duplicate of this bug. ***
