Completely mindboggling...
$ sudo dnf -v update [sudo] password for chris: Loaded plugins: builddep, config-manager, copr, debug, debuginfo-install, download, generate_completion_cache, needs-restarting, playground, repoclosure, repograph, repomanage, reposync DNF version: 2.5.1 cachedir: /var/cache/dnf repo: using cache for: updates-testing updates-testing: using metadata from Thu 20 Jul 2017 07:08:22 PM MDT. repo: using cache for: updates updates: using metadata from Thu 20 Jul 2017 09:22:17 AM MDT. repo: using cache for: fedora not found updateinfo for: Fedora 26 - x86_64 fedora: using metadata from Fri 07 Jul 2017 06:38:55 AM MDT. repo: using cache for: google-chrome not found deltainfo for: google-chrome not found updateinfo for: google-chrome google-chrome: using metadata from Wed 19 Jul 2017 11:37:49 AM MDT. Last metadata expiration check: 1:05:51 ago on Sat 22 Jul 2017 10:05:21 AM MDT. That's metadata that's 2-3 days stale. The current metadata from just 45 minutes ago is in /var/tmp/dnf-chris-pl3hc0v6/ It's almost like the problem is it's bouncing between /var/cache/dnf and /tmp/var/dnf* and sometimes it updates one or the other, gets confused, and it's really really... ... eyebrow raising. Chris Murphy _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
