On Thu, Nov 7, 2024 at 4:57 PM Jonathan Billings billings@negate.org wrote:
On Nov 6, 2024, at 17:11, Stephen Morris steve.morris.au@gmail.com wrote:
why was that updated again, surely that repository was flagged as up to date by the prior dnf update?
Not 100% sure but I suspect something in dnf needs-restarting is looking for the extra dnf metadata that includes package file lists, which aren’t downloaded for normal updates, to speed up regular updates (since they’re significantly larger metadata files).
Just like when you run “dnf install httpd” it only downloads the smaller set of information, but if you then run “dnf install /usr/bin/top” it has to download more metadata, even though you just updated a moment ago.
If stale metadata is the case, then rebuilding the dnf cache with the --refresh option may sidestep the problem. Something like `sudo dnf makecache --refresh`. Also see https://dnf.readthedocs.io/en/latest/command_ref.html#metadata-synchronization.
Jeff