+1, since switching to DNF on Rawhide I've had to run 'dnf clean expire-cache' every time I wanted to get any updates, which kind of defeats the point.

Hey guys, you are powerusers who need the updates very often. Few of the regular users do. In DNF we depart from the traditional direction of most Fedora projects (making the developer community happy) towards making the users happy.

Closing this as WONTFIX. Note you can tweak the config files to obtain the desired expiry times.

Me thinks the rawhide repo config (in fedora-release-rawhide) should set metadata_expire to an appropriate value instead of relying whatever the package manager default happens to be. Dnf's 48h default is indeed much too long for rawhide, but also yum's 6h default is unnecessarily short for rawhide as well.

This has nothing to do with the supposed dichotomy between users and power users.  Regular users don't use Rawhide anyway.  I don't understand why the default in Dnf can't be set to a more appropriate value instead of overriding it via feodra-release-rawhide but anyway, I am reassigning this bug to fedora-release.

Rahul: i think the suggestion to do it in the repo definition makes sense, actually, logically speaking. Our contention is 'expiry time should be short for Rawhide'. The package manager only implements a universal default expiry time, which inevitably can't be perfect for all repos. So indeed if we think the expiry time for a specific repo which we control ought to be a specific value, we should be stating that in fedora-release, not making it dnf's universal default for repos which don't specify one.

Sure.  I don't particularly care how it is done as long as the values are more reasonable for Rawhide users.

This is unreasonable and will penalize people who, unlike Adam, do not need to do daily updates of the hottest&latest packages. I advise the releng team to refuse this change (which can easily slip into f21 after branching).

That is silly.  If you are running rawhide, you want the latest packages.  Not two day old ones.

It can't 'easily slip into f21 after branching', with NoFrozenRawhide. Rawhide is always Rawhide, and Rawhide's .repo files are always Rawhide's .repo files. They're in fedora-release-rawhide and fedora-release is not derived from it.

https://fedoraproject.org/wiki/Releases/Rawhide :

"As a rawhide consumer, you should:

    Be willing to update on an almost daily basis. Rawhide gets hundreds of updates a day, and applying those updates on a regular basis allows you to more easily troubleshoot issues."

Created attachment 846220 [details]
Here's a patch.