On Tue, 2023-08-29 at 10:09 +0530, Sumantro Mukherjee wrote:
On Wed, Aug 16, 2023 at 10:40 PM Adam Williamson adamwill@fedoraproject.org wrote:
On Wed, 2023-08-16 at 19:57 +0530, Sumantro Mukherjee wrote:
Hey Folks!
Toolbx is very necessary and is becoming very important. It provides the basic and core functionality for many users who use immutable OS as daily driver for installing apps with dnf. In many cases, help devs manage deps, libs and envs. Functional breakage of Toolbx causes distress and many folks might be actually running apps inside and if after "dnf update" things fall apart[0], that's great
UX.
I want to mark Toolbx rpm as crit-path.. thoughts? Any ideas on how to go about this?
Well, per my change to the critpath definition recently:
https://fedoraproject.org/w/index.php?title=Critical_path_package&diff=6... (this was proposed and agreed in 2022 but I forgot to change it), the thing to do would be to get one or more editions, spins or labs to declare that toolbx is critpath for them. -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw@fosstodon.org https://www.happyassassin.net
Hey Adam,
We have the ack from Workstation Working Group [0] It's still not implemented and I would like to learn how to do it! :) Any guidance will be awesome :D
You send a PR for fedora-comps, adding it to the critical-path-gnome group:
https://pagure.io/fedora-comps/blob/main/f/comps-f39.xml.in#_784
make sure to keep it in alphabetical order. Probably do it for both comps-f39.xml.in and comps-f40.xml.in.
After that, the critical path definition will be updated within 24 hours and any updates with the package in created after that will be marked as critical path.