14 day thresholds for some packages in Bodhi #13251

New issue

Open

opened 2026-03-03 08:30:34 +00:00 by slaanesh · 5 comments

slaanesh commented

2026-03-03 08:30:34 +00:00

Hello,

I've pushed some updates for various packages over time, and some packages / branch combination have a weird staging time in Bodhi; I can't figure out the logic behind it, where this is set and how to change it.

Example:

dpkg - 14 days for Stable in fc42/fc43/fc44 branches, epel branches have 7 days.
egl-wayland - 14 days in Stable for fc42 only, all the other branches have 7 days.

None of those packages is critical or particularly special. dpkg is used only to manipulate deb packages for inspection (and was also abandoned before I started updating it), the second one is a small library used only by the proprietary NVIDIA driver, so it's never installed as part of anything else.

Thanks.

Hello, I've pushed some updates for various packages over time, and some packages / branch combination have a weird staging time in Bodhi; I can't figure out the logic behind it, where this is set and how to change it. Example: - `dpkg` - 14 days for Stable in `fc42/fc43/fc44` branches, `epel` branches have 7 days. - `egl-wayland` - 14 days in Stable for `fc42` only, all the other branches have 7 days. None of those packages is critical or particularly special. `dpkg` is used only to manipulate deb packages for inspection (and was also abandoned before I started updating it), the second one is a small library used only by the proprietary NVIDIA driver, so it's never installed as part of anything else. Thanks.

kevin commented

2026-03-03 17:41:32 +00:00

Owner

This is due to them being in the critical path. dpkg for lots of releases, egl-wayland for just f42.

I am not sure why they are listed, you can look at
https://forge.fedoraproject.org/releng/tooling/src/branch/main/quality-assurance/critpath/critpath.py

This is due to them being in the critical path. dpkg for lots of releases, egl-wayland for just f42. I am not sure why they are listed, you can look at https://forge.fedoraproject.org/releng/tooling/src/branch/main/quality-assurance/critpath/critpath.py

slaanesh commented

2026-03-04 07:12:42 +00:00

Author

Where is the actual critical path list defined? I've tried dnf group info on all the groups listed at https://forge.fedoraproject.org/releng/tooling/src/branch/main/quality-assurance/critpath/critpath.py#L39, but the packages are not there.

Where is the actual critical path list defined? I've tried `dnf group info` on all the groups listed at https://forge.fedoraproject.org/releng/tooling/src/branch/main/quality-assurance/critpath/critpath.py#L39, but the packages are not there.

kevin commented

2026-03-04 22:58:53 +00:00

Owner

It's all the things in the indicated groups in that script and their dependencies.

I am not sure where these specific ones are coming from. They definitely seem wrong. ;)

Perhaps @adamwill has some better way to debug this?

It's all the things in the indicated groups in that script and their dependencies. I am not sure where these specific ones are coming from. They definitely seem wrong. ;) Perhaps @adamwill has some better way to debug this?

adamwill commented

2026-03-05 00:21:48 +00:00

Contributor

Not really, you just have to do detective work.

I suspect the cause in the dpkg case is that kiwi-systemdeps requires kiwi-systemdeps-core, and kiwi-systemdeps-core recommends dpkg. critpath.py doesn't explicitly specify whether or not to include soft dependencies; it goes with whatever the Python dnf library default behavior is. I think the default is to include recommends. I can look at tweaking it to not include those and see how the output would differ.

Not really, you just have to do detective work. I suspect the cause in the `dpkg` case is that `kiwi-systemdeps` requires `kiwi-systemdeps-core`, and `kiwi-systemdeps-core` recommends `dpkg`. critpath.py doesn't explicitly specify whether or not to include soft dependencies; it goes with whatever the Python `dnf` library default behavior is. I think the default is to include recommends. I can look at tweaking it to not include those and see how the output would differ.

slaanesh commented

2026-03-05 09:46:48 +00:00

Author

Thanks. I remember there were more packages in this condition, but I don't remember right now.

It's a bit weird that dpkg is in the critical path, it was basically abandoned for a long time before I picked it up. I use it for some simple manipulation in pipelines running on Fedora at work.

Regarding egl-wayland, would be nice to have that as well out of the critical path. Once upon a time, it was used at build time to provide EGLStream path for the NVIDIA driver in Xwayland and mutter, but that has long gone. The EGLStream code path was last used in NVIDIA driver 470, and that has long gone EOL. Any newer version did not use that, so I pushed to get it unlinked in Fedora and CentOS Stream/RHEL 10 (during the beta). I think the leftover critical path is due to its past use for this.

Whenever we push a new NVIDIA driver out (I work for NVIDIA), I'm updating as well the EGL libraries (egl-ex11/egl-gbm/egl-wayland/egl-wayland2) in Fedora/EPEL to match, and waiting 2 weeks between a driver release and it's supporting libraries it's suboptimal.

Thanks.

Thanks. I remember there were more packages in this condition, but I don't remember right now. It's a bit weird that `dpkg` is in the critical path, it was basically abandoned for a long time before I picked it up. I use it for some simple manipulation in pipelines running on Fedora at work. Regarding `egl-wayland`, would be nice to have that as well out of the critical path. Once upon a time, it was used at build time to provide EGLStream path for the NVIDIA driver in Xwayland and mutter, but that has long gone. The EGLStream code path was last used in NVIDIA driver 470, and that has long gone EOL. Any newer version did not use that, so I pushed to get it unlinked in Fedora and CentOS Stream/RHEL 10 (during the beta). I think the leftover critical path is due to its past use for this. Whenever we push a new NVIDIA driver out (I work for NVIDIA), I'm updating as well the EGL libraries (`egl-ex11/egl-gbm/egl-wayland/egl-wayland2`) in Fedora/EPEL to match, and waiting 2 weeks between a driver release and it's supporting libraries it's suboptimal. Thanks.