Tom Horsley writes:
I ran "dnf -y update" this morning. It said the last metadata update was 8 days ago and there was nothing to do. I then ran "dnf clean all" and "dnf -y update" again and it is loading 414 new updates. What really bad setting is it consulting to think that 8 day old metadata is up to date, and where the heck do I fix it?
Something's definitely not quite right with DNF's caching in F29.I have a local LAN repository whose metadata_expire is intentionally set to one minute, because as soon as I have a new package to install I push it into the repository and then I want to have the update installed immediately.
Even when I explicitly specify --refresh dnf will often tell me that the metadata was refresh only a few hours ago, and that's it's done.
Ok, well, that's definitely more than a minute. I just run the same "dnf upgrade --refresh" command a second time. This always makes dnf redownload the repo and see the updated packages, since its metadata is older than the set expiration interval.
This was more stable in F28. dnf reliably refreshed the cached metadata when it expired. I can't quite work out what's up with dnf now. Sometimes it refreshes the expired metadata. Sometimes it does that only on a 2nd attempt. There's no rhyme or reason to it.
Attachment:
pgp6naYAjfPHw.pgp
Description: PGP signature
_______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
