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