Stabilize dev-libs/nettle-2.1
All good x86.
dev-lang/pike will not build with any version of dev-libs/nettle-2*, so stabilisation is moot. However, there is a version not-yet-in-tree available that claims to support it. Removing all arches, until this is resolved...
Nettle is the default crypto backend of GnuTLS 2.12.
amd64 ok
amd64 done. Thanks Agostino
Faulis complaint is still true here! There is no version of dev-lang/pike in the tree that builds with dev-libs/nettle-2.1!
(In reply to comment #6) dev-libs/nettle-2.0 is already stable, so it's natural to stabilize dev-libs/nettle-2.1.
(In reply to comment #7) > (In reply to comment #6) > > dev-libs/nettle-2.0 is already stable, so it's natural to stabilize > dev-libs/nettle-2.1. Yes, but if someone installs pike, it will alway downgrade nettle again...
(In reply to comment #8) > (In reply to comment #7) > > (In reply to comment #6) > > > > dev-libs/nettle-2.0 is already stable, so it's natural to stabilize > > dev-libs/nettle-2.1. > Yes, but if someone installs pike, it will alway downgrade nettle again... So, file a stabilisation request for newer pike. If I am not mistaken this should break the vicious circle.
Stable on alpha.
ppc stable
(In reply to comment #9) > (In reply to comment #8) > > (In reply to comment #7) > > > (In reply to comment #6) > > > > > > dev-libs/nettle-2.0 is already stable, so it's natural to stabilize > > > dev-libs/nettle-2.1. > > Yes, but if someone installs pike, it will alway downgrade nettle again... > > So, file a stabilisation request for newer pike. If I am not mistaken this > should break the vicious circle. Unfortunately the newest version in the tree (although just ~x86 atm) is also the latest upstream and it carries a DEPEND="<=dev-libs/nettle-2.0" with it. Pike itself doesn't have stable rdeps... so maybe it would be the best to also drop stable on pike for the moment?!
(In reply to comment #12) > Unfortunately the newest version in the tree (although just ~x86 atm) is also > the latest upstream and it carries a DEPEND="<=dev-libs/nettle-2.0" with it. > Pike itself doesn't have stable rdeps... so maybe it would be the best to also > drop stable on pike for the moment?! Ok, so I checked again. The newest pike is compatible with 2.0, so it should go stable anyway. I haven't checked if nettle 2.1 is covered, too. So: Newer pike has to go stable. Newer nettle only if it works with pike.
(In reply to comment #13) > Ok, so I checked again. The newest pike is compatible with 2.0, so it should > go stable anyway. I haven't checked if nettle 2.1 is covered, too. So: > > Newer pike has to go stable. > Newer nettle only if it works with pike. I tried to build the newest pike once with nettle-2.1 (modified the ebuild to not downgrade...) without any luck! :-(
Stable for HPPA.
arm/sparc stable
ppc64 stable (as dev-lang/pike is not even keyworded for the arch, the issues raised here don't concern us)
x86 will pass.
ia64/s390/sh stable, closing