Description of problem: With dnf's more aggressive caching behavior, I find myself constantly doing "dnf clean expire-cache" before "dnf update" because I want to be absolutely sure I get the latest updates before going through the trouble to reboot, especially when there is a 0-day security vulnerability that has an update I want to be sure to get. Rather than requiring "dnf clean expire-cache" every time, it would be helpful to know how update the cache is, and then using that information to decide whether a cache flush is necessary. So I propose an enhancement to dnf to show the timestamp of the dnf cache before every operation. Version-Release number of selected component (if applicable): dnf-0.6.3-2.fc21.noarch
Charles, you can do `dnf update --refresh` instead of `dnf clean expire-cache && dnf update`. *** This bug has been marked as a duplicate of bug 1170156 ***