----- Original Message ----- > From: "Radek Holy" <rholy@xxxxxxxxxx> > To: "Community support for Fedora users" <users@xxxxxxxxxxxxxxxxxxxxxxx> > Sent: Thursday, July 23, 2015 9:01:24 AM > Subject: Re: dnf update vs Software Udpates > > > > ----- Original Message ----- > > From: "Ron Yorston" <rmy@xxxxxxxxxxxx> > > To: users@xxxxxxxxxxxxxxxxxxxxxxx > > Sent: Wednesday, July 22, 2015 8:20:11 PM > > Subject: Re: dnf update vs Software Udpates > > > > Suvayu Ali wrote: > > >That said, I sometimes do not understand what's the harm in getting > > >updates few hours later. dnf already tells you how old the metadata is > > >when it starts, you can choose to get the latest metadata if it is too > > >old. So what's the big deal? > > > > I certainly get the impression that dnf tells me about updates less > > frequently than yum did. It also seems to pull in metadata less > > frequently. > > > > In fedora-updates.repo I have: metadata_expire=6h. I also have the > > dnf-makecache.timer 'masked'. > > > > It's more than 6 hours since I last ran dnf but: > > > > [root@vulcan rmyf22]# dnf check-update > > Fedora 22 - x86_64 - RMY repository 131 kB/s | 6.0 kB 00:00 > > Last metadata expiration check performed 0:00:00 ago on Wed Jul 22 08:38:32 > > 2015. > > [root@vulcan rmyf22]# > > > > No updates. It pulled in metadata for my private repo but not > > fedora-updates. So is it really telling me "how old the metadata is"? > > The message just refers to the last time an expiration check was > > performed. Does that mean the metadata was up to date as of 0:00:00 ago? > > Because, as we shall see, it clearly wasn't. > > No, precisely, it tells you the maximum of all timestamps of caches of all > repositories. I mean, if the cache of "fedora" is 3 hours old, the cache of > "updates" is 2 hours old and the cache of "updates-testing" is 1 hour old, > the output is 1 hour. ...which means that 1 hour ago, DNF found out that only "updates-testing" is expired (according to "metadata_expire"). I mean, there might be updates in another repositories as well but DNF is allowed to check it only after the "metadata_expire" period. > To see all the timestamps, you should use "--debug". Maybe you can help us by > filling an RFE with a suggestion of a better message? > > > Let's try the --refresh option: > > > > [root@vulcan rmyf22]# dnf --refresh check-update > > Fedora 22 - x86_64 - RMY repository 113 kB/s | 6.0 kB 00:00 > > Last metadata expiration check performed 0:00:00 ago on Wed Jul 22 08:39:01 > > 2015. > > [root@vulcan rmyf22]# > > > > Still no updates. Time for a bigger hammer (don't try this at home or > > offer it as advice to newbies): > > > > [root@vulcan rmyf22]# rm -rf /var/cache/dnf/x86_64/22/updates* > > [root@vulcan rmyf22]# dnf check-update > > Fedora 22 - x86_64 - Updates 774 kB/s | 12 MB 00:16 > > Last metadata expiration check performed 0:00:16 ago on Wed Jul 22 08:40:02 > > 2015. > > > > environment-modules.x86_64 3.2.10-16.fc22 > > updates > > ... > > > > Plus 55 other updates. What's going on? > > > > Ron > > -- > > 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 > > > > -- > Radek Holý > Associate Software Engineer > Software Management Team > Red Hat Czech -- Radek Holý Associate Software Engineer Software Management Team Red Hat Czech -- 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
