Bug 1185651

Summary:	RFE: display timestamp of cache
Product:	[Fedora] Fedora	Reporter:	Charles R. Anderson <cra>
Component:	dnf	Assignee:	Packaging Maintenance Team <packaging-team-maint>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	21	CC:	akozumpl, jsilhan, mluscon, packaging-team-maint, pnemade, rholy, tim.lauridsen
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-01-26 14:53:34 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Charles R. Anderson 2015-01-25 14:17:54 UTC

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

Comment 1 Honza Silhan 2015-01-26 14:53:34 UTC

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 ***