Current key expires 2025-12-31. $ gpg2 --show-key /etc/pki/rpm-gpg/RPM-GPG-KEY-Mageia pub rsa4096 2011-02-07 [SCEA] [expires: 2025-12-31] 00EDB89585B012A8916F0DF8B742FA8B80420F66 uid Mageia Packages <packages@mageia.org>
mageia-repos-9-4.1.mga9 in core/updates_testing should fix the issue. $ rpm -qa mageia-repos-keys mageia-repos-keys-9-4.1.mga9 $ gpg2 --show-key /etc/pki/rpm-gpg/RPM-GPG-KEY-Mageia pub rsa4096 2011-02-07 [SCEA] [expires: 2029-12-31] 00EDB89585B012A8916F0DF8B742FA8B80420F66 uid Mageia Packages <packages@mageia.org>
Assignee: bugsquad => qa-bugs
SRPMS: mageia-repos-9-4.1.mga9 RPMS: mageia-repos-9-4.1.mga9 mageia-repos-cauldron-9-4.1.mga9 mageia-repos-keys-9-4.1.mga9 mageia-repos-pkgprefs-9-4.1.mga9
Thanks for spotting! - and fixing immediately! Selecting updates in drakrpm brought the three packages except the cauldron one. $ rpm -qa mageia-repos-keys mageia-repos-keys-9-4.1.mga9 $ gpg2 --show-key /etc/pki/rpm-gpg/RPM-GPG-KEY-Mageia pub rsa4096 2011-02-07 [SCEA] [går ut: 2029-12-31] 00EDB89585B012A8916F0DF8B742FA8B80420F66 uid Mageia Packages <packages@mageia.org> Test OK also: I could remove all configured repos, and add a fresh set using urpmi.addmedia I wonder, to facilitate upgrading to mga10, an idea would be to make that one install as a dependency, would that solve the issue? (Note this is not my cup of tea...)
Assignee: qa-bugs => bugsquadCC: (none) => fri, marja11, sysadmin-bugsPriority: Normal => High
This is a separate thing than 'broken' RPM signing key that prevents upgrading from mga9 to mga10 with urpmi without manual interaction. /etc/pki/rpm-gpg/RPM-GPG-KEY-Mageia is only used with tools like mock.
Blocks: (none) => 34920
(In reply to Jani Välimaa from comment #4) > This is a separate thing than 'broken' RPM signing key that prevents > upgrading from mga9 to mga10 with urpmi without manual interaction. > /etc/pki/rpm-gpg/RPM-GPG-KEY-Mageia is only used with tools like mock. Bug 34920 is more for tracking that one.
Before the update: [tom@localhost ~]$ rpm -qa mageia-repos-keys mageia-repos-keys-9-4.mga9 [tom@localhost ~]$ gpg2 --show-key /etc/pki/rpm-gpg/RPM-GPG-KEY-Mageia pub rsa4096 2011-02-07 [SCEA] [expires: 2025-12-31] 00EDB89585B012A8916F0DF8B742FA8B80420F66 uid Mageia Packages <packages@mageia.org> After the update: [tom@localhost ~]$ rpm -qa mageia-repos-keys mageia-repos-keys-9-4.1.mga9 [tom@localhost ~]$ gpg2 --show-key /etc/pki/rpm-gpg/RPM-GPG-KEY-Mageia pub rsa4096 2011-02-07 [SCEA] [expires: 2029-12-31] 00EDB89585B012A8916F0DF8B742FA8B80420F66 uid Mageia Packages <packages@mageia.org> Looks good here on 64-bit.
CC: (none) => andrewsfarmWhiteboard: (none) => MGA9-64-OK
Also good for i586. Validating.
Keywords: (none) => validated_updateWhiteboard: MGA9-64-OK => MGA9-64-OK MGA9-32-OK
Thanks for the quick fixing Jani! And info. / Regarding flags in this bug I happened to set them by accident in comment 3 because I initially was trying responding to comment 0 but that did never get posted so flags was set for another circuntance... Bugzilla have been really slow today, Forum and Wiki seemed to be offline and mail list sends me double mails... /
Installed and tested without issues. System: Mageia 9, x86_64, AMD Ryzen 5 5600G with Radeon Graphics $ uname -a Linux jupiter 6.6.116-desktop-1.mga9 #1 SMP PREEMPT_DYNAMIC Mon Nov 3 15:35:03 UTC 2025 x86_64 GNU/Linux $ rpm -qa | grep mageia-repos- mageia-repos-keys-9-4.1.mga9 mageia-repos-pkgprefs-9-4.1.mga9 mageia-repos-9-4.1.mga9 $ gpg2 --show-key /etc/pki/rpm-gpg/RPM-GPG-KEY-Mageia pub rsa4096 2011-02-07 [SCEA] [expires: 2029-12-31] 00EDB89585B012A8916F0DF8B742FA8B80420F66 uid Mageia Packages <packages@mageia.org>
CC: (none) => mageiaKeywords: validated_update => (none)Whiteboard: MGA9-64-OK MGA9-32-OK => MGA9-64-OK
Keywords: (none) => advisory
HP Pavilion 15 laptop,AMD A8-4555, MGA9-64 Plasma. No installation issues. After the update: [tom@localhost ~]$ rpm -qa mageia-repos-keys mageia-repos-keys-9-4.1.mga9 [tom@localhost ~]$ gpg2 --show-key /etc/pki/rpm-gpg/RPM-GPG-KEY-Mageia gpg: WARNING: unsafe permissions on homedir '/home/tom/.gnupg' pub rsa4096 2011-02-07 [SCEA] [expires: 2029-12-31] 00EDB89585B012A8916F0DF8B742FA8B80420F66 uid Mageia Packages <packages@mageia.org> Not sure what it doesn't like about the permissions in the home directory, but it seems to be OK, anyway.
Edited advisory to add info about mock
Looks like this can go, then. Validating.
Whiteboard: MGA9-64-OK => MGA9-64-OK MGA9-32-OKKeywords: (none) => validated_update
Actually mock seems to be using /usr/share/distribution-gpg-keys/mageia/RPM-GPG-KEY-Mageia. It's dnf that is using /etc/pki/rpm-gpg/RPM-GPG-KEY-Mageia. So I'll need to update also distribution-gpg-keys for mga9.
Keywords: validated_update => (none)
Updated distribution-gpg-keys-1.89-1.1.mga9 in core/updates testings also fixes expiring /usr/share/distribution-gpg-keys/mageia/RPM-GPG-KEY-Mageia. $ gpg2 --show-key /usr/share/distribution-gpg-keys/mageia/RPM-GPG-KEY-Mageia pub rsa4096 2011-02-07 [SCEA] [expires: 2029-12-31] 00EDB89585B012A8916F0DF8B742FA8B80420F66 uid Mageia Packages <packages@mageia.org> SRPMS: distribution-gpg-keys-1.89-1.1.mga9 mageia-repos-9-4.1.mga9 RPMS: distribution-gpg-keys-1.89-1.1.mga9 mageia-repos-9-4.1.mga9 mageia-repos-cauldron-9-4.1.mga9 mageia-repos-keys-9-4.1.mga9 mageia-repos-pkgprefs-9-4.1.mga9
Source RPM: mageia-repos-9-4.mga9 => mageia-repos-9-4.mga9, distribution-gpg-keys-1.89-1.mga9
I not find issues building with mock before & after update If that is enough test please restore OK and validation
Advisory updated
Better to get this one FIXED.
Keywords: (none) => validated_update
An update for this issue has been pushed to the Mageia Updates repository. https://advisories.mageia.org/MGAA-2025-0108.html
Resolution: (none) => FIXEDStatus: NEW => RESOLVED
Keywords: (none) => IN_ERRATA9
Keywords: (none) => IN_RELEASENOTES10