almost certainly a stupid question, but how do i force "dnf update" to consult the latest mirrors to see the new packages now available?
i can *see* here:
http://dl.fedoraproject.org/pub/fedora/linux/updates/testing/22/x86_64/n/
the new NetworkManager rpm that solves a particular problem i've run into, but no variation of "dnf update" i run will pick it up.
what's the secret recipe?
rday
sudo dnf config-manager --set-enabled updates-testingshould enable the repo you need.
---- On Thu, 20 Aug 2015 16:41:32 -0400 Robert P. J. Day <rpjday@crashcourse.ca> almost certainly a stupid question, but how do i force "dnf update" to consult the latest mirrors to see the new packages now available?
i can *see* here:
http://dl.fedoraproject.org/pub/fedora/linux/updates/testing/22/x86_64/n/
the new NetworkManager rpm that solves a particular problem i've run into, but no variation of "dnf update" i run will pick it up.
what's the secret recipe?
rday
On Thu, 20 Aug 2015, Zach Villers wrote:
sudo dnf config-manager --set-enabled updates-testing should enable the repo you need.
no, my updates-testing repo *is* enabled ... i'm asking about an obvious time lag from the time i see those rpms in the repo, and when my local dnf command finally sees them.
rday
On Thu, 20 Aug 2015 17:25:25 -0400 (EDT) "Robert P. J. Day" rpjday@crashcourse.ca wrote:
no, my updates-testing repo *is* enabled ... i'm asking about an obvious time lag from the time i see those rpms in the repo, and when my local dnf command finally sees them.
So, if you look at:
http://dl.fedoraproject.org/pub/fedora/linux/updates/testing/22/x86_64/repod...
you can see the repomd.xml file was created today at 19:43 UTC time.
So, thats the time when the repo was "live" on the master mirrors.
Next, mirrormanager has to crawl the tree and see what changed and update it's db of 'current' repodata. It starts crawls when it sees a message something changed, but it can take it a few hours depending on how much changed.
Once thats done, hourly there is a static file updated from the db and synced out to the mirrorlist servers. Once that pushes out with the new repomd.xml info in it you should see it in metalinks.
While thats going on, mirrors are mirroring the master mirror on whatever schedule they do.
So, it can take a few hours at least.
kevin
Try refreshing your local cache: # dnf clean metadata expire-cache. If that doesn't work, a # dnf clean all should do it. If you still doesn't see the packages you're looking for then you'll have to wait for your mirrors to sync up.
On Thu, Aug 20, 2015 at 6:31 PM Kevin Fenzi kevin@scrye.com wrote:
On Thu, 20 Aug 2015 17:25:25 -0400 (EDT) "Robert P. J. Day" rpjday@crashcourse.ca wrote:
no, my updates-testing repo *is* enabled ... i'm asking about an obvious time lag from the time i see those rpms in the repo, and when my local dnf command finally sees them.
So, if you look at:
http://dl.fedoraproject.org/pub/fedora/linux/updates/testing/22/x86_64/repod...
you can see the repomd.xml file was created today at 19:43 UTC time.
So, thats the time when the repo was "live" on the master mirrors.
Next, mirrormanager has to crawl the tree and see what changed and update it's db of 'current' repodata. It starts crawls when it sees a message something changed, but it can take it a few hours depending on how much changed.
Once thats done, hourly there is a static file updated from the db and synced out to the mirrorlist servers. Once that pushes out with the new repomd.xml info in it you should see it in metalinks.
While thats going on, mirrors are mirroring the master mirror on whatever schedule they do.
So, it can take a few hours at least.
kevin
users mailing list users@lists.fedoraproject.org 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