| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| 01-use-invoke-rc-d.diff | # Use invoke-rc.d instead of service command. # Closes: #850948 diff -Naur needrestart-2.11.orig/needrestart needrestart-2.11/needrestart |
no | ||||
| 02-bash-term-in-posix-shell.diff | # Workaround needrestart: bash-term-in-posix-shell '& read -p' [etc/needrestart/restart.d/dbus.service:65] diff -Naur needrestart-3.6.orig/ex/restart.d/dbus.service needrestart-3.6/ex/restart.d/dbus.service |
no | ||||
| 03-ignore-serial-getty.diff | do not restart serial-getty@*.service | Helmut Grohne <helmut@subdivi.de> | no | |||
| 04-vm-detection.diff | [PATCH] Fix VM detection regression introduced in f54d85c | zxyrepf <53189615+zxyrepf@users.noreply.github.com> | no | 2022-07-24 | ||
| 05-fix-AMD-ucode-checking-in-non-debug-mode.patch | [PATCH] fix AMD ucode checking in non-debug mode It looks like the assignment when the ucode exist was not done *unless* `debug` (`-v`) was set. Therefore, all AMD microcode checks were returning UNKNOWN, including in Nagios checks, unless the `-v` ("verbose", but actually `debug`) was passed. |
=?UTF-8?q?Antoine=20Beaupr=C3=A9?= <anarcat@debian.org> | no | 2023-11-15 | ||
| 06-uCode-fix-uninitialized-value-in-logging-of-processo.patch | [PATCH] [uCode] fix uninitialized value in logging of processor index This got broken in f8c2609f8d5a0e10bd988497b8ea9815a7bb2fa8. Before that it would have effectively logged `$processors{$pid}->{processor}`, but the `processor` entry is also the key in `%processors`, i.e. equals `$pid`. |
=?UTF-8?q?Stefan=20B=C3=BChler?= <source@stbuehler.de> | no | 2023-05-28 | ||
| 07-mark-unavailable-firmware-as-CURRENT.patch | [PATCH] mark unavailable firmware as CURRENT This changes the policy of reporting missing firmware updates as "UNKNOWN". Now, if there's no available firmware, we report "current". That fixes needrestart on platforms that do not have firmware support (#220) or platforms that *are* supported but for which a CPU is to new to have an updated firmware available (#149). It does *not* create a new "unavailable" status (#274) as this maps poorly in Nagios reporting, but that is an option that was considered here as well. |
=?UTF-8?q?Antoine=20Beaupr=C3=A9?= <anarcat@debian.org> | no | 2023-11-21 |