> And here's proof of what can happen with just --refresh: > > 1. dnf update > 2. dnf update --refresh > 3. dnf update --refresh > > The last run reverts to older metadata with only 50 updates available compared > with earlier. Mirror manager assigning to an out-of-date mirror? A day later, no matter how often I run "dnf update --refresh", it never gets access to the newer metadata from yesterday again. Not the 76 packages as shown earlier in this thread, only the older 50. So, indeed, there's something seriously wrong here, and I assume it can only be fixed if the developers of mirror manager and dnf come together and look into it. After giving the "dnf clean expire-cache" option another try, too, and then the hammer "dnf clean metadata", there has been a fresh download of even newer metadata compared with yesterday: [...] Install 4 Packages Upgrade 111 Packages Remove 3 Packages Total download size: 211 M [...] # rpm -q dnf dnf-1.1.0-2.fc24.noarch -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
