On 4/11/24 09:09, Samuel Sieb wrote:
On
11/3/24 1:57 PM, Stephen Morris wrote:
On 4/11/24 08:52, Samuel Sieb wrote:
On 11/3/24 1:35 PM, Stephen Morris
wrote:
When I issued the command sudo
dnf upgrade needs-restarting, it updated and loaded all the
repositories and said there was nothing to do.
When I issued the command immediately after the above
one, sudo dnf needs-restarting, it updated and loaded all
the repositories again and said "No core libraries or
services have been updated since boot-up. Reboot should not
be necessary".
When I issue the command immediately after the 2nd
command above, sudo dnf upgrade, It loaded all the
repositories and then said there were 193 packages to
upgrade and 195 packages to replace.
Given that there were updates to put on why did the
first command not put the updates on and then display
whether or not as a result a restart was required and for
which packages?
Your first command was telling dnf to upgrade a package called
"needs- restarting". You can only give dnf one command at a
time.
Nothing to do with dnf5. That's how it's always worked.
Does this mean that with the tracer addin no longer working
there is no way to get the equivalent functionality with dnf at
update time?
How did you do this before? The only difference between dnf4 and
dnf5 is that dnf4 will actually tell you that there's no package
called "needs-restarting" where dnf5 just says there's nothing to
do. You also showed that the "needs-restarting" command is also
working, so there's no issue here.
In dnf4 I was using the tracer plugin, which seems to not work in
dnf5, so in dnf4 the needs-restarting was not required, although in
dnf4 I don't remember seeing needs-restarting as a command when
issuing dnf --help.
With the plugins not working I was expecting to be able to issue
both commands at once and get the equivalent functionality to the
tracer plugin.
regards,
Steve