On Sun, 2024-11-03 at 19:02 -0500, Jeffrey Walton wrote: > > As I posted in a separate thread on Friday last, I think that both the > > command 'tracer' and the corresponding dnf5 plugin are broken. I've > > been waiting to see if anyone contradicts this but so far no-one has, > > so I may post a BZ report. It seems to me a serious regression. > > Looks OK to me for the case that no reboot is necessary. The behavior > follows what the man page says. > > $ dnf needs-restarting > Updating and loading repositories: > Fedora 41 - x86_64 100% | 10.8 MiB/s | 98.1 MiB | 00m09s > Fedora 41 - x86_64 - Updates 100% | 11.4 MiB/s | 20.4 MiB | 00m02s > Fedora 41 OpenH264 (from Cisco) - x86_ 100% | 6.0 KiB/s | 8.1 KiB | 00m01s > Repositories loaded. > No core libraries or services have been updated since boot-up. > Reboot should not be necessary. > > $ echo $? > 0 > > But I don't have a machine that needs a reboot at the moment, so that > case was not tested. A kernel update should tickle that case. I was really talking about 'tracer', which for me definitely isn't working. I find tracer more useful because it tells me about anything that's out of date, not just system reboots or service restarts. At least it used to when it worked. And as it's still present in F41 the fact that it doesn't work is concerning. poc -- _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
