Le 03/11/2026 à 22:20, Felix Miata via tde-devels a écrit :
[...] In 45, I force upgraded to trinity-repo-14.1.7-1.fc45.noarch.rpm and avoided the gpg errors, but same packages conflict and have broken dependencies as 44
Hello Felix, yes, since I've renewed the gpg signing key, including for the package containing the key itself, you cannot simply upgrade packages as usual.
I think the simplest solution is to de-configure the current Trinity repositories and configure again according to the wiki, it should update the GPG key.
Regards
François