Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1950041 - PackageKit metadata refresh fail: .repo file metadata_expire changes
Summary: PackageKit metadata refresh fail: .repo file metadata_expire changes
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: PackageKit
Version: 34
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Richard Hughes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 1903294
TreeView+ depends on / blocked
 
Reported: 2021-04-15 15:52 UTC by Rex Dieter
Modified: 2021-04-16 16:10 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Rex Dieter 2021-04-15 15:52:10 UTC 
Could be a feature not a bug, but thought I'd mention in case it's possible to address.

While testing PK metadata cache issues, I found a case where dnf and PK metadata cache's were out of sync (not uncommon).  dnf reported a pkg foo from repo bar had an update available, but PK didn't refresh yet.  The Packagekit metadata was somewhere between 12-24hrs old, at least by eyeballing timestamps of stuff under /var/cache/PackageKit/

As a test, I went to the bar.repo file and added
metadata_expire=1h

and ran:
pkcon refresh

I was expecting PackageKit to refresh the repo bar metadata and report and update available, except it didn't. :(
Comment 1 Neal Gompa 2021-04-15 16:18:50 UTC 
The only change I've seen here on this is: https://github.com/hughsie/PackageKit/commit/54a616b8edb8391f90ae183989bd98aa87e26b14

Prior to that was my change to read all repo and var directories: https://github.com/hughsie/PackageKit/commit/ed73aa6317595d2c2f1bda7990cbd64efb133f84

Neither of which should have had an impact on this...
Note You need to log in before you can comment on or make changes to this bug.