[François] Mageia upgrade from 9 to 10 refuses to upgrade any TDE packages due to signature key not trusted
Mageia 10 was released yesterday, but upgrading from freshly upgraded 9 32bit, it refuses to upgrade any trinity rpm due to NOT TRUSTED signature key
As urpmi --auto-update downloaded all v10 packages, I was able to force install them with rpm, which was very tedious, but TDE & TDM are working.
Le 01/07/2026 à 03:12, Felix Miata via tde-devels a écrit :
Mageia 10 was released yesterday, but upgrading from freshly upgraded 9 32bit, it refuses to upgrade any trinity rpm due to NOT TRUSTED signature key
As urpmi --auto-update downloaded all v10 packages, I was able to force install them with rpm, which was very tedious, but TDE & TDM are working.
Hello Felix,
Yes, I've finally seen the same problem after upgrading my actual computer to Mageia 10. What I don't understand is why I did not see this when I tried in virtual machines ...
So, I've generated a new GPG key and re-signed all mga10 packages. Wait for the mirrors to be synchronized then try again the installation procedure. You may need to manually clear your urpmi cache then remove/re-add the repository.
urpmi --clean urpmi.removemedia trinity trinity-noarch urpmi.addmedia trinity http://mirror.ppa.trinitydesktop.org/trinity/rpm/mga10/trinity-r14/RPMS/x86_... urpmi.addmedia trinity-noarch http://mirror.ppa.trinitydesktop.org/trinity/rpm/mga10/trinity-r14/RPMS/noar...
Regards François
François Andriot composed on 2026-07-02 11:49 (UTC+0200):
Felix Miata wrote:
Mageia 10 was released yesterday, but upgrading from freshly upgraded 9 32bit, it refuses to upgrade any trinity rpm due to NOT TRUSTED signature key
As urpmi --auto-update downloaded all v10 packages, I was able to force install them with rpm, which was very tedious, but TDE & TDM are working.
Yes, I've finally seen the same problem after upgrading my actual computer to Mageia 10. What I don't understand is why I did not see this when I tried in virtual machines ...
So, I've generated a new GPG key and re-signed all mga10 packages. Wait for the mirrors to be synchronized then try again the installation procedure. You may need to manually clear your urpmi cache then remove/re-add the repository.
urpmi --clean urpmi.removemedia trinity trinity-noarch urpmi.addmedia trinity http://mirror.ppa.trinitydesktop.org/trinity/rpm/mga10/trinity-r14/RPMS/x86_... urpmi.addmedia trinity-noarch http://mirror.ppa.trinitydesktop.org/trinity/rpm/mga10/trinity-r14/RPMS/noar...
Something's still wrong. Following instructions on https://wiki.mageia.org/en/Mageia_10_Release_Notes#Online-Upgrade.2C_using_urpmi_.28CLI.29 eliminates the repo configuration for TDE. Proceeding with those instructions with no TDE configuration nevertheless results in a virtually continuous flood of either error: message lines that end with your email address or declarations of certificate policy violations or SHA1 is not considered secure or no binding signature or others as it proceeds to upgrade all Mageia's packages. This is apparently no different than has been happening in recent weeks and longer following your instructions on installations already upgraded from 9 to 10 between 3 and 7 months before 10 was released one month ago. The current one nearing halfway complete is on i686 host gx28b, not a VM.
Le 30/07/2026 à 01:33, Felix Miata via tde-devels a écrit :
Something's still wrong. Following instructions on https://wiki.mageia.org/en/Mageia_10_Release_Notes#Online-Upgrade.2C_using_urpmi_.28CLI.29 eliminates the repo configuration for TDE. Proceeding with those instructions with no TDE configuration nevertheless results in a virtually continuous flood of either error: message lines that end with your email address or declarations of certificate policy violations or SHA1 is not considered secure or no binding signature or others as it proceeds to upgrade all Mageia's packages. This is apparently no different than has been happening in recent weeks and longer following your instructions on installations already upgraded from 9 to 10 between 3 and 7 months before 10 was released one month ago. The current one nearing halfway complete is on i686 host gx28b, not a VM.
Hello Felix, apparently when removing the the Trinity repositories, the Trinity GPG key remains installed.
Before upgrading to Mageia 10, I suggest you remove the Trinity for mageia 9 key manually:
# rpmkeys --delete 2ab131c6-51b4e35f
This should avoid displaying messages about invalid SHA1 keys. But I've not tested.
François
-
Felix Miata -
François Andriot