Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 834925 - net-p2p/freenet-0.7.5_p1491-r1: stabilisation
Summary: net-p2p/freenet-0.7.5_p1491-r1: stabilisation
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Stabilization (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Thomas Sachau
URL:
Whiteboard:
Keywords: CC-ARCHES
Depends on: 834924
Blocks:
  Show dependency tree
 
Reported: 2022-03-10 20:39 UTC by Sam James
Modified: 2022-03-13 20:24 UTC (History)
0 users

See Also:
Package list:
net-p2p/freenet-0.7.5_p1491-r1 amd64 net-libs/NativeThread-0_pre20190914-r1 amd64
Runtime testing required: ---
nattka: sanity-check+


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sam James archtester Gentoo Infrastructure gentoo-dev Security 2022-03-10 20:39:50 UTC
Thanks!
Comment 1 NATTkA bot gentoo-dev 2022-03-10 20:44:22 UTC Comment hidden (obsolete)
Comment 2 NATTkA bot gentoo-dev 2022-03-11 12:56:27 UTC Comment hidden (obsolete)
Comment 3 Thomas Sachau gentoo-dev 2022-03-12 07:57:07 UTC
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?
Comment 4 Jakov Smolić archtester gentoo-dev 2022-03-12 11:49:41 UTC
amd64 done

all arches done
Comment 5 Sam James archtester Gentoo Infrastructure gentoo-dev Security 2022-03-13 20:24:46 UTC
(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.