Tests pass for me on amd64 with all USE flags enabled. I cannot build or test on arm64, ppc, ppc64, or x86. Compilation on arm (armv6j, Raspberry Pi 1) with all stable deps has completed successfully for me, but I am still running the tests. (They take several hours on a Raspberry Pi 1.) I will report the result here after the tests have completed.
Sanity check failed: > net-p2p/bitcoin-core-27.1 > depend arm64 stable profile default/linux/arm64/23.0 (12 total) > >=net-libs/libnatpmp-20220705:= > depend arm64 dev profile default/linux/arm64/23.0/hardened (10 total) > >=net-libs/libnatpmp-20220705:= > rdepend arm64 stable profile default/linux/arm64/23.0 (12 total) > >=net-libs/libnatpmp-20220705:= > rdepend arm64 dev profile default/linux/arm64/23.0/hardened (10 total) > >=net-libs/libnatpmp-20220705:=
All sanity-check issues have been resolved
Sanity check failed: > net-p2p/bitcoin-core-27.1 > depend ppc stable profile default/linux/ppc/23.0 (8 total) > >=dev-libs/libsecp256k1-0.4.0:=[ellswift,extrakeys,recovery,schnorr] > depend ppc dev profile default/linux/ppc/23.0/musl (2 total) > >=dev-libs/libsecp256k1-0.4.0:=[ellswift,extrakeys,recovery,schnorr] > rdepend ppc stable profile default/linux/ppc/23.0 (8 total) > >=dev-libs/libsecp256k1-0.4.0:=[ellswift,extrakeys,recovery,schnorr] > rdepend ppc dev profile default/linux/ppc/23.0/musl (2 total) > >=dev-libs/libsecp256k1-0.4.0:=[ellswift,extrakeys,recovery,schnorr]
All tests passed on arm (armv6j, Raspberry Pi 1).
Sanity check failed: > net-p2p/bitcoin-core-27.1 > depend arm64 stable profile default/linux/arm64/23.0 (12 total) > >=dev-libs/libsecp256k1-0.4.0:=[ellswift,extrakeys,recovery,schnorr] > depend arm64 dev profile default/linux/arm64/23.0/hardened (10 total) > >=dev-libs/libsecp256k1-0.4.0:=[ellswift,extrakeys,recovery,schnorr] > rdepend arm64 stable profile default/linux/arm64/23.0 (12 total) > >=dev-libs/libsecp256k1-0.4.0:=[ellswift,extrakeys,recovery,schnorr] > rdepend arm64 dev profile default/linux/arm64/23.0/hardened (10 total) > >=dev-libs/libsecp256k1-0.4.0:=[ellswift,extrakeys,recovery,schnorr]
arm done
arm64 done
amd64 done
x86 done
Was any of these new-to-stabilise arches requested by anyone? Why are we stabilising arm, ppc at this point? Why not simply roll over existing stable keywords?
> # eshowkw bitcoin-core > Keywords for net-p2p/bitcoin-core: > | | u | > | a a p s a l r | n | > | m r h p p l o m i s m | e u s | r > | d a m p p c a x p o i s 3 6 | a s l | e > | 6 r 6 p p 6 r 8 h n p c 9 8 | p e o | p > | 4 m 4 a c 4 c 6 a g s v 0 k | i d t | o > --------+-----------------------------+-------+------- > 25.1-r2 | + ~ ~ o ~ ~ o + o o o o o o | 8 # 0 | gentoo > 25.2 | ~ ~ ~ o ~ ~ o ~ o o o o o o | 8 # | gentoo > 26.0-r1 | ~ ~ ~ o ~ ~ o ~ o o o o o o | 8 # | gentoo > 26.1 | + ~ ~ o ~ ~ o ~ o o o o o o | 8 # | gentoo > 26.2 | ~ ~ ~ o ~ ~ o ~ o o o o o o | 8 # | gentoo > 27.0 | ~ ~ ~ o ~ ~ o ~ o o o o o o | 8 # | gentoo > 27.1 | + + + o ~ ~ o + o o o o o o | 8 o | gentoo > 27.2 | ~ ~ ~ o ~ ~ o ~ o o o o o o | 8 # | gentoo > 28.0 | ~ ~ ~ o ~ ~ o ~ o o o o o o | 8 o | gentoo
(In reply to Andreas Sturmlechner from comment #12) > Was any of these new-to-stabilise arches requested by anyone? Why are we > stabilising arm, ppc at this point? Why not simply roll over existing stable > keywords? I don't know what you mean. Sam asked me to request stabilization of my package, so I did. Does Gentoo typically ignore some architectures for stabilization purposes? Should I be requesting stabilization on only a subset of the supported arches?
Almost all packages are stabilised only on a subset of packages. How big that subset is comes down to historic stabilisations, maintainer discretion, user requests, revdep requirements, arch viability [life time, upstream care re arch specific bug fixes, test failures, ...] etc. "Please stabilise new version" colloquially means roll over stable keywords where currently stable for this package. In order to stabilise for new arches, that's fine, but we'd usually expect a declaration of intent in $summary or #comment 1. This bug, as you can see from my eshowkw output, would have been "done" after amd64 and x86 arch team had finished their work, and all older versions are overshadowed, so already eligible for cleanup since 2024-11-09.
(In reply to Andreas Sturmlechner from comment #15) > Almost all packages are stabilised only on a subset of packages. *subset of arches
