Thanks!
Sanity check failed: > net-p2p/freenet-0.7.5_p1491-r1 > pdepend amd64 dev profile default/linux/amd64/17.0/x32 (2 total) > net-libs/NativeThread:0 > pdepend amd64 stable profile default/linux/amd64/17.1 (14 total) > net-libs/NativeThread:0 > rdepend amd64 dev profile default/linux/amd64/17.0/x32 (2 total) > net-libs/nativebiginteger:0 > rdepend amd64 stable profile default/linux/amd64/17.1 (14 total) > net-libs/nativebiginteger:0
Sanity check failed: > net-p2p/freenet-0.7.5_p1491-r1 > pdepend amd64 dev profile default/linux/amd64/17.0/x32 (2 total) > net-libs/NativeThread:0 > pdepend amd64 stable profile default/linux/amd64/17.1 (14 total) > net-libs/NativeThread:0
Any specific reason why you want this package to get stable keyword? The freenet developers themselves consider the package experimental and new versions may break all existing versions at the moment they come out. In addition, if you request a stable keyword, why limit this to amd64 while the package also has x86 keyword?
amd64 done all arches done
(In reply to Thomas Sachau from comment #3) > Any specific reason why you want this package to get stable keyword? The > freenet developers themselves consider the package experimental and new > versions may break all existing versions at the moment they come out. > We have a similar situation with e.g. signal-desktop-bin, discord, and some others (like youtube-dl/ytdlp). It's okay in such situations to request immediate stabilisation of the new version, even if it's not been 30 days. That said, AFAIK, the Freenet developers don't expect *immediate* upgrades (as in: breakage usually doesn't happen with 0 notice and 0 grace period). > In addition, if you request a stable keyword, why limit this to amd64 while > the package also has x86 keyword? I don't think we need to request stabilisation for every keyworded arch. I think this is useful on amd64 for myself included, but I don't know if anyone wants it on x86, so I'd rather wait until someone asks.