Description of problem: I've configured the same repositories in URPMI and DNF, but DNF doesn't find the updates. This issue doesn't always happen, but sometimes. Steps to Reproduce: 1. Run "# urpmi --auto-update" [01/12/2018 23_44] # urpmi --auto-update medium "Core Release2" is up-to-date medium "Core Updates" is up-to-date medium "Nonfree Release2" is up-to-date medium "Nonfree Updates" is up-to-date medium "Tainted Release" is up-to-date medium "Tainted Updates" is up-to-date medium "Core 32bit Release" is up-to-date medium "Core 32bit Updates" is up-to-date medium "Nonfree 32bit Release" is up-to-date medium "Nonfree 32bit Updates" is up-to-date medium "Tainted 32bit Release" is up-to-date medium "Tainted 32bit Updates" is up-to-date medium "google-chrome" is up-to-date To satisfy dependencies, the following packages are going to be installed: Package Version Release Arch (medium "Core Updates") lib64vorbis0 1.3.5 2.1.mga6 x86_64 lib64vorbisenc2 1.3.5 2.1.mga6 x86_64 lib64vorbisfile3 1.3.5 2.1.mga6 x86_64 (medium "Nonfree Updates") flash-player-plugin 28.0.0.137 1.mga6.nonfr> x86_64 1KB of additional disk space will be used. 216KB of packages will be retrieved. Proceed with the installation of the 4 packages? (Y/n) n 2. Run "# dnf update" [01/12/2018 23_44] # dnf update Last metadata expiration check: 7:54:08 ago on Fri 12 Jan 2018 15:33:42 WET. Dependencies resolved. Nothing to do. Complete!
Is "Core Release2" the same mirror as used in dnf? It looks odd.
CC: (none) => zen25000
Now both are in automatic mode. But I've also tried with ftp://ftp.free.fr/mirrors/mageia.org/distrib/6/x86_64/media/core/release and it's the same.
(In reply to Hurr from comment #2) > Now both are in automatic mode. But I've also tried with > ftp://ftp.free.fr/mirrors/mageia.org/distrib/6/x86_64/media/core/release and > it's the same. I suppose you changed "release" in that link to "updates" for the updates repository? (In reply to Hurr from comment #0) > Description of problem: > > I've configured the same repositories in URPMI and DNF, but DNF doesn't find > the updates. This issue doesn't always happen, but sometimes. > > > 2. Run "# dnf update" > > [01/12/2018 23_44] > # dnf update > > Last metadata expiration check: 7:54:08 ago on Fri 12 Jan 2018 15:33:42 WET. > * lib*vorbis* was pushed 12-01-18 20:50 * your metadata were older, so no wonder dnf couldn't see lib64vorbis* * please use the following command to update while refreshing the metadata: dnf upgrade --refresh
CC: (none) => marja11Keywords: (none) => NEEDINFOAssignee: bugsquad => ngompa13
Summary: DNF doesn't allways find the updates => DNF doesn't always find the updates
Yes, I have "release" in core repository and "updates" in updates repository: # cat /etc/yum.repos.d/mageia-x86_64.repo [mageia-x86_64] name=Mageia $releasever - x86_64 baseurl=ftp://ftp.free.fr/mirrors/mageia.org/distrib/6/x86_64/media/core/release #metalink=https://mirrors.mageia.org/metalink?distrib=mageia-$releasever&arch=x86_64§ion=core&repo=release #mirrorlist=https://www.mageia.org/mirrorlist/?release=$releasever&arch=x86_64§ion=core&repo=release gpgcheck=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-Mageia failovermethod=priority enabled=1 [updates-x86_64] name=Mageia $releasever - x86_64 - Updates baseurl=ftp://ftp.free.fr/mirrors/mageia.org/distrib/6/x86_64/media/core/updates #metalink=https://mirrors.mageia.org/metalink?distrib=mageia-$releasever&arch=x86_64§ion=core&repo=updates #mirrorlist=https://www.mageia.org/mirrorlist/?release=$releasever&arch=x86_64§ion=core&repo=updates gpgcheck=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-Mageia failovermethod=priority enabled=1 After running "dnf upgrade --refresh", now dnf finds more updates than urpmi: # urpmi --auto-update medium "Core Release2" is up-to-date medium "Core Updates" is up-to-date medium "Nonfree Release2" is up-to-date medium "Nonfree Updates" is up-to-date medium "Tainted Release" is up-to-date medium "Tainted Updates" is up-to-date medium "Core 32bit Release" is up-to-date medium "Core 32bit Updates" is up-to-date medium "Nonfree 32bit Release" is up-to-date medium "Nonfree 32bit Updates" is up-to-date medium "Tainted 32bit Release" is up-to-date medium "Tainted 32bit Updates" is up-to-date medium "google-chrome" is up-to-date To satisfy dependencies, the following packages are going to be installed: Package Version Release Arch (medium "Core Updates") lib64vorbis0 1.3.5 2.1.mga6 x86_64 lib64vorbisenc2 1.3.5 2.1.mga6 x86_64 lib64vorbisfile3 1.3.5 2.1.mga6 x86_64 (medium "Nonfree Updates") flash-player-plugin 28.0.0.137 1.mga6.nonfr> x86_64 1KB of additional disk space will be used. 216KB of packages will be retrieved. Proceed with the installation of the 4 packages? (Y/n) n # dnf update Last metadata expiration check: 1 day, 1:39:58 ago on Fri 12 Jan 2018 15:33:42 WET. Dependencies resolved. Nothing to do. Complete! # dnf upgrade --refresh Mageia 6 - i586 - Updates 2.7 MB/s | 14 MB 00:05 Mageia 6 - x86_64 - Nonfree - Updates 29 kB/s | 37 kB 00:01 Mageia 6 - x86_64 - Updates 2.6 MB/s | 13 MB 00:05 Mageia 6 - i586 - Nonfree - Updates 20 kB/s | 32 kB 00:01 Last metadata expiration check: 0:00:00 ago on Sat 13 Jan 2018 17:14:51 WET. Dependencies resolved. ====================================================================================================================================================== Package Arch Version Repository Size ====================================================================================================================================================== Upgrading: cpupower x86_64 4.14.13-1.mga6 updates-x86_64 168 k dracut x86_64 044-11.1.mga6 updates-x86_64 278 k flash-player-plugin x86_64 28.0.0.137-1.mga6.nonfree updates-x86_64-nonfree 29 k kernel-desktop-devel-latest x86_64 4.14.13-1.mga6 updates-x86_64 62 k kernel-desktop-latest x86_64 4.14.13-1.mga6 updates-x86_64 62 k kernel-userspace-headers x86_64 4.14.13-1.mga6 updates-x86_64 1.0 M ldetect-lst x86_64 0.3.7.5-1.mga6 updates-x86_64 1.2 M lib64vorbis0 x86_64 1.3.5-2.1.mga6 updates-x86_64 91 k lib64vorbisenc2 x86_64 1.3.5-2.1.mga6 updates-x86_64 75 k lib64vorbisfile3 x86_64 1.3.5-2.1.mga6 updates-x86_64 21 k microcode noarch 0.20180108-1.mga6.nonfree updates-x86_64-nonfree 1.2 M vboxadditions-kernel-desktop-latest x86_64 5.2.2-7.mga6 updates-x86_64 24 k virtualbox-kernel-desktop-latest x86_64 5.2.2-7.mga6 updates-x86_64 24 k Installing dependencies: kernel-desktop-4.14.13-1.mga6 x86_64 1-1.mga6 updates-x86_64 55 M kernel-desktop-devel-4.14.13-1.mga6 x86_64 1-1.mga6 updates-x86_64 10 M vboxadditions-kernel-4.14.13-desktop-1.mga6 x86_64 5.2.2-7.mga6 updates-x86_64 156 k virtualbox-kernel-4.14.13-desktop-1.mga6 x86_64 5.2.2-7.mga6 updates-x86_64 189 k Transaction Summary ====================================================================================================================================================== Install 4 Packages Upgrade 13 Packages Total download size: 70 M Is this ok [y/N]: n
This is basically caused by how servers synchronize updates. Some of them do --delete-before to conserve space, which wipes out the content of the repodata dir until after the fetch is complete. The reason this happens with DNF data is because the filenames of the repodata files are unique each time they are generated, rather than being the same and being updated in place. Most of our mirrors follow our rsync option recommendation[1], but some don't. This would be properly fixed with the deployment of MirrorBrain and moving the DNF mirrorlist to become a metalink (see bug 17400). [1]: https://wiki.mageia.org/en/Mirrors_policy#Rsync_options
Keywords: NEEDINFO => (none)See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=17400
Closing as dupe of bug 17400. *** This bug has been marked as a duplicate of bug 17400 ***
Status: NEW => RESOLVEDResolution: (none) => DUPLICATESee Also: https://bugs.mageia.org/show_bug.cgi?id=17400 => (none)