I cannot upgrade using dnf with updates_testing enabled. There are multiple mismatches between metadata and packages listed in the QA database since a few days. Kernel 5.1.17 is offered. Version no. should be 5.1.18. Best regards, Ulrich
Created attachment 11193 [details] CLI output of test upgrade
Version: 7 => unspecifiedComponent: RPM Packages => OthersAssignee: bugsquad => sysadmin-bugsProduct: Mageia => InfrastructureCC: (none) => sysadmin-bugs
See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=24726CC: (none) => tmb
Works again since Friday morning, 19-07-2019.
Status: NEW => RESOLVEDResolution: (none) => WORKSFORME
Created attachment 11234 [details] CLI output of test upgrade Again another mismatch since about 2 days. # urpmi --auto-upgrade works as tested in a VM. # dnf upgrade works with upgrades_testing disabled. As I said before, dnf metadata should be generated and monitored automatically. Ulrich
Attachment 11193 is obsolete: 0 => 1
Reopened
Resolution: WORKSFORME => (none)Status: RESOLVED => REOPENED
Working again since Sunday evening, 2019-08-04.
Created attachment 11265 [details] CLI output of test upgrade Another mismatch when trying to test https://bugs.mageia.org/show_bug.cgi?id=25349 mesa-19.1.5-2.mga7 should be available since 2019-08-25. Ulrich
Working again since 2019-08-29. Upgraded 3 times (1 real hardware, 2 VMs)
Created attachment 11272 [details] CLI output of test upgrade Another mismatch spotted on 2019-09-09. kernel-desktop-5.2.13-1.mga7-1-1.mga7.x86_64.rpm should be available in update-testing since 2019-09-08.
Working again since 2019-09-13. I guess that metadata are refreshed and synced, when a bunch of packages is moved from updates_testing to testing.
Created attachment 11355 [details] CLI output of test upgrade Another mismatch on 11/11, which is not yet resolved 2 days later. BTW there were other issues not documented here.
Created attachment 11802 [details] CLI output of test upgrade Kernel 5.7.14-1.mga7 should be available since 2020-08-07, but still it is not. This is a long standing issue. I did not comment it at any occurrence. Ulrich
Are you using mirrorlist or baseurl in /etc/yum.repos.d/mageia-x86_64.repo? What if you use dnf update --refresh?
CC: (none) => ghibomgx
I use mirrorlist as it is default. Never changed anything in this regard. You see the output of # dnf upgrade --refresh (nothing to do) -> attachment comment#11.
According to timestamp in the tier 1 mirror, repodata seems outdated: http://distrib-coffee.ipsl.jussieu.fr/pub/linux/Mageia/distrib/7.1/x86_64/media/core/updates_testing/repodata/ with respect to: http://distrib-coffee.ipsl.jussieu.fr/pub/linux/Mageia/distrib/7.1/x86_64/media/core/updates_testing/media_info/
CC: (none) => pterjan
Yesterday # dnf upgrade --refresh ran a successful upgrade of 60 packages. It looks as if metadata are refreshed manually when shifting packages from updates_testing to testing.
Created attachment 12900 [details] Occurrence: Testing 29357 glibc Still valid in current MGA 8 updates_testing The bugreport is already set ok. I still cannot download the package list.
Attachment 11234 is obsolete: 0 => 1 Attachment 11265 is obsolete: 0 => 1 Attachment 11272 is obsolete: 0 => 1
(In reply to Ulrich Beckmann from comment #15) > Yesterday # dnf upgrade --refresh ran a successful upgrade of 60 packages. > > It looks as if metadata are refreshed manually when shifting packages from > updates_testing to testing. * shifting packages from updates_testing to updates.