I have been using 1.5.8 and 1.5.9 on amd64 and arm stable systems with success for a while now. Could it be stabilized so I can cleanup my keywords file ? :)
Arches, please go ahead, stabilizeand remove youreself from Cc when done ;)
Hum, no arches CCed :)
Adding arch teams that had a previously stable version. Adding arm as I am using this on a raspberrypi as well.
Thanks for adding. I just marked them but forgot to hit the "Add arches" button ;)
=net-dns/unbound-1.5.10 is already stable for amd64...
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
An automated check of this bug failed - repoman reported dependency errors: > dependency.bad net-dns/unbound/unbound-1.5.10.ebuild: DEPEND: arm(default/linux/arm/13.0) ['dev-libs/fstrm[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?]', 'net-dns/ldns-utils[examples]', 'dev-util/splint'] > dependency.bad net-dns/unbound/unbound-1.5.10.ebuild: RDEPEND: arm(default/linux/arm/13.0) ['dev-libs/fstrm[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?]', 'net-dns/dnssec-root']
*** Bug 602862 has been marked as a duplicate of this bug. ***
An automated check of this bug failed - repoman reported dependency errors: > dependency.bad net-dns/unbound/unbound-1.5.10.ebuild: DEPEND: arm(default/linux/arm/13.0) ['net-dns/ldns-utils[examples]', 'dev-util/splint'] > dependency.bad net-dns/unbound/unbound-1.5.10.ebuild: RDEPEND: arm(default/linux/arm/13.0) ['net-dns/dnssec-root']
ppc ppc64 stable.
arm stable.
An automated check of this bug succeeded - the previous repoman errors are now resolved.
x86 stable Last arch, closing...