Max Pyziur wrote:
> 
> Greetings,
> 
> When updating via dnf update I get the following error messages:
> The GPG keys listed for the "Signal Messaging Devel Project (Fedora_40)"
> repository are already installed but they are not correct for this package.
> Check that the correct key URLs are configured for this repository.. Failing
> package is: nodejs-electron-30.3.0-2.13.x86_64
>  GPG Keys are configured as: 
> https://download.opensuse.org/repositories/network:/im:/signal/Fedora_40/repodata/repomd.xml.key
> Public key for signal-desktop-7.19.0-1.1.x86_64.rpm is not trusted. Failing
> package is: signal-desktop-7.19.0-1.1.x86_64
>  GPG Keys are configured as: 
> https://download.opensuse.org/repositories/network:/im:/signal/Fedora_40/repodata/repomd.xml.key
> Public key for signal-libringrtc-2.45.0-1.1.x86_64.rpm is not trusted.
> Failing package is: signal-libringrtc-2.45.0-1.1.x86_64
>  GPG Keys are configured as: 
> https://download.opensuse.org/repositories/network:/im:/signal/Fedora_40/repodata/repomd.xml.key
> 
> 
> Any guidance here would be appreciated.

Those keys may be using an algorithm or have various
properties which the newer rpm signature verification
library doesn't like.

I don't know what the policies are for rpm with the sequoia
library backend, so this could be way off.

Another possibility is that the keys have been updated since
you initially installed them and you need to remove the
current key to allow dnf to import the updated key.

-- 
Todd

Attachment: signature.asc
Description: PGP signature

-- 
_______________________________________________
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to