[Feature] Include extra "`STATIC`" packages

[jcpunk]

The article https://access.redhat.com/solutions/27943 includes a number of common libraries that are so widely used that a reboot would be beneficial.

The most obvious ones are probably glibc and linux-firmware...

These are pared down a bit but listed for dnf at: https://github.com/rpm-software-management/dnf-plugins-core/blob/master/plugins/needs_restarting.py#L42

[FrostyX]

Thank you for the ticket @jcpunk.
I was about to do

--- a/data/applications.xml
+++ b/data/applications.xml
@@ -183,4 +183,24 @@
        <app name="sudo" ignore="ignore" />
        <app name="su" ignore="ignore" />

+
+       <!--
+          - These packages require reboot as per
+          - https://access.redhat.com/solutions/27943
+          - See also the `NEED_REBOOT` variable in `needs_restarting`
+          - https://github.com/rpm-software-management/dnf-plugins-core/blob/master/plugins/needs_restarting.py
+       -->
+       <group type="static">
+               <app name="kernel" />
+               <app name="kernel-core" />
+               <app name="kernel-rt" />
+               <app name="glibc" />
+               <app name="linux-firmware" />
+               <app name="systemd" />
+               <app name="dbus" />
+               <app name="dbus-broker" />
+               <app name="dbus-daemon" />
+               <app name="microcode_ctl" />
+       </group>
+
 </applications>

but it won't be that easy, unfortunately. Because this matches on process names, not package names.

[jcpunk]

I'll confess, I thought the static packages were just package checks...

…

On Thu, Dec 11, 2025, 4:52 PM Jakub Kadlčík ***@***.***> wrote: *FrostyX* left a comment (FrostyX/tracer#226) <#226 (comment)> Thank you for the ticket @jcpunk <https://github.com/jcpunk>. I was about to do --- a/data/applications.xml+++ b/data/applications.xml@@ -183,4 +183,24 @@ <app name="sudo" ignore="ignore" /> <app name="su" ignore="ignore" /> ++ <!--+ - These packages require reboot as per+ - https://access.redhat.com/solutions/27943+ - See also the `NEED_REBOOT` variable in `needs_restarting`+ - https://github.com/rpm-software-management/dnf-plugins-core/blob/master/plugins/needs_restarting.py+ -->+ <group type="static">+ <app name="kernel" />+ <app name="kernel-core" />+ <app name="kernel-rt" />+ <app name="glibc" />+ <app name="linux-firmware" />+ <app name="systemd" />+ <app name="dbus" />+ <app name="dbus-broker" />+ <app name="dbus-daemon" />+ <app name="microcode_ctl" />+ </group>+ </applications> but it won't be that easy, unfortunately. Because this matches on process names, not package names. — Reply to this email directly, view it on GitHub <#226 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA2673SOA23VWWRUJ3FPNXT4BHYUTAVCNFSM6AAAAACN3B4PVGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTMNBUGEYTSOBWGU> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[jcpunk]

My testing on RHEL9 shows:

• glibc actually works as expected, no need to list explicitly
• systemd actually works as expected, no need to list explicitly
• dbus is not detected by tracer for restart (no files in rpm)
• dbus-broker is not detected by tracer for restart (%post in rpm appears to install, but not kick it)
• dbus-daemon is not detected by tracer for restart (%post in rpm appears to install, but not kick it)
• microcode_ctl is not detected by tracer for restart
• linux-firmware is not detected by tracer for reboot

Additionally, elrepo provides a kernel-ml and kernel-lt which can provide an alternate kernel.

This doesn't really help provide a "how to detect", but at least drops a few items from the list.

I suspect something similar to https://github.com/FrostyX/tracer/blob/master/tracer/resources/tracer.py#L126 may be required...

FWIW: the debian world seems to use linux-image-xyz for their kernel packages.