Description of problem: When upgrading around once a week, dnf holds onto its cache and gets 404 errors on mirrors fairly regularly (I don't remember this happening with yum). Would it be possible to at least run a HEAD query on the repodata to see if it should be downloaded? Version-Release number of selected component (if applicable): dnf-0.5.2-1.fc20.noarch
Hello, thank you for the report. We'll take a look.
Ben, can you please post a specific failure you've seen?
Created attachment 911627 [details] Shell log from a stale dnf cache An attempt at installing perf after ~a week of not touching dnf. Note that there is no downloaded data for any remote repository and the repomd.xml is stating that it is newer than the cached files.
This is an issue with the fedora-rawhide-kernel-nodebug repo[1]: it is refreshed (supposedly) daily, but the metadata expire is left to the default 48 hours. Note that 24 hours is not enough in this case and the setting should be 0, i.e.: metadata_expire = 0 Otherwise there is a always a chance the client will run into a just refreshed repo. Please contact the repo maintainer to do the appropriate fix. Thank you. inb4 decrease the default. [1] http://fedoraproject.org/wiki/RawhideKernelNodebug