Stable on amd64
Stable on alpha.
sparc stable (thanks to Rolf Eike Beer)
I wouldn't agree that this was ready for a stable listing,as it won't
compile against openssl-1.1.0g
(In reply to Geoff Madden from comment #8)
> I wouldn't agree that this was ready for a stable listing,as it won't
> compile against openssl-1.1.0g
OpenSSL 1.1 isn't stable.
(In reply to Michał Górny from comment #9)
> (In reply to Geoff Madden from comment #8)
> > I wouldn't agree that this was ready for a stable listing,as it won't
> > compile against openssl-1.1.0g
> OpenSSL 1.1 isn't stable.
problem is no matter what I request to happen as far as openssl is concerned,eventually 1.1.0g gets pulled in by something then all hell breaks loose with packages not compiling.
On looking in the zz-autounmask file I see I have placed an item for openssl-1.1.0g-bindist, have now removed same and will let you know of results, it seems I have created my own problem,I have checked the dir's in /etc/portage and removed all changes referring openssl,replaced autounmask-write with -keep-masks,now the system is updating.
This stabilized it for all already:
Author: Mike Gilbert <firstname.lastname@example.org>
Date: Mon Dec 4 11:00:46 2017 -0500
dev-lang/python: stabilize nis disablement for 2.7 and 3.5
Package-Manager: Portage-2.3.15, Repoman-2.3.6_p7
fwiw, I believe it still fails tests on arm64, but all versions do and for python2 it's probably a libffi issue and not a regression; python-2.7.14-r1 has been good in practice. UnCCing arm64 as already stable