Yarn and Sury APT keys issues

Hi everyone !

You might have issues with your system updates :wrench:. Here are the usual error messages:

W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://packages.sury.org/php bookworm InRelease: The following signatures were invalid: EXPKEYSIG B188E2B695BD4743 DEB.SURY.ORG Automatic Signing Key
W: GPG error: https://dl.yarnpkg.com/debian stable InRelease: The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY 62D54FD4003F6525
E: The repository ‘https://dl.yarnpkg.com/debian stable InRelease’ is not signed.

Don’t panic ! There is an easy fix. You’ll just need a shell access (e.g via `ssh`) to your server.

Once you are logged in as admin, run:

sudo rm /etc/apt/trusted.gpg.d/{yarn,extra_php_version}.gpg
sudo yunohost tools regen-conf apt

And that’s all ! :tada:

To check that the fix is working, re-run the search of updates:

sudo apt update

We’ll try to find an automatic fix for the future but that’s not the easiest thing.

34 Likes
:jack_o_lantern: YunoHost 13.0 / Trixie spooky beta
Castopod broke attempting upgrade
FreshRSS failed to install, 404 when trying to get php8.4
Baikal failed backup when upgrading
PluXml demande php8.0 : puis-je l'installer sans risque?
Nextcloud update failed because a safety backup could not be created
Can't Re-install Collabora - coolwsd systemd error
Nextcloud update failed because a safety backup could not be created
Nextcloud update failed because a safety backup could not be created
Worpress upgrade failed
Problèmes mise à jours roundcube et paheko
WordPress install went bad Now getting a 502 bad gateway and no way to reverse
Nextcloud doesn't run after unsuccessful upgrade
Mise à jour d'Immich vers la version 2.5.6~ynh8 a échoué
Mise à jours WordPress plantée
Migration failing from
Nextcloud injoignable suite à une mise à jour 32.0.5~ynh1 -> 32.0.6~ynh2
Nextcloud injoignable suite à une mise à jour 32.0.5~ynh1 -> 32.0.6~ynh2
Baikal failed backup when upgrading
Echec de mise à jour de RoundCube
Failed setup change Nginx to Angie
Roundcube Upgrade/Install fails
Pixelfed upgrade failure - Backup can't be made
Nextcloud upgrade 31.0.11~ynh1 to 32.0.6~ynh1 failed, restoring the preupgrade backup also fails
Baikal failed backup when upgrading
WordPress install went bad Now getting a 502 bad gateway and no way to reverse
Aborting the upgrade, because a safety backup could not be created (Échec de la collecte des fichiers à sauvegarder)
Nextcloud Uprade is not working
Impossible to install apps
Nextcloud warning about php version after last nextcloud update
NextCloud update from 32.0.7~ynh1 to 33.0.2~ynh1 fails due to repository signature issues

It seems it’s official to do that :

apt-get install extrepo
extrepo enable sury
2 Likes

In the absence of an autofix, would it be possible to add a diagnostic tool?
With the link to the thread :slight_smile:

Je ne suis pas sûr que cela fasse bon ménage avec un sudo yunohost tools regen-conf apt : il va y avoir deux clés (différentes a priori) pour un seul dépôt. Cela va poser problème.

I think this will cause a key mismatch when the sudo yunohost tools regen-conf apt command will be run : two (different, I guess) keys for a single repo : there will be an issue IMHO.