Opening this to track reverse dependencies for stable.
Mike, what do you think about pushing OpenSSL 1.0.0a-r3 stable now? I don't see any open bugs related to it anymore.
- The pyopenssl testsuite failure is caused by openssl syntax change, and doesnt effect on it's functionality in anyway. It's known upstream, but upstream seems very dead for that package. Also, it haven't stopped other distros from moving forward (Fedora, for instance).
- The open bugs listed here, are stabilization requests with only ppc and hppa in CC lists.
i'm not sure openssl-1 has seen testing across all arches yet. we just fixed alpha failures in the last few days to let it compile.
for the main arches (x86/amd64), i dont see a problem, but the others will probably want to settle for a bit.
it sort of sucks to push it stable for only selected arches, so i'm willing to wait a bit longer to get all CC'd at once
Please test and stabilize:
dev-libs/openssl-0.9.8o-r2: amd64 x86
dev-libs/openssl-1.0.0a-r3: alpha amd64 arm hppa ia64 m68k ppc ppc64 s390 sh sparc x86
@alpha: Your fix has been in tree for 14 days, take your time in testing...
@hppa/ppc: The blocking bugs are fixing build-time issues at first. I'd say revision bump was never necessary on the remaining ones... but it's been done, so please take care.
This will sort out firefox/xulrunner needing cups built with USE gnutls (bug 325469).
ppc64 stable for 1.0.0a-r3
amd64 stable for 1.0.0a-r3 (and 0.9.8o-r2 for acroread, nxclient and chromium-bin)
Stable on alpha. The foolscap failure doesn't concern us since it isn't keywords. The other blockers have either been resolved for alpha or don't concern us, either.
Stable for HPPA PPC.
x86 stable, closing