You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since the expiration of the key qgis-2017.gpg.key, it is not possible anymore to install packages from ubuntu-ltr-2.18 or debian-ltr-2.18.
sudo apt-get update
[...]
Err :7 https://qgis.org/ubuntu-ltr-2.18 cosmic InRelease
Les signatures suivantes ne sont pas valables : EXPKEYSIG CAEB3DC3BDF7FB45 QGIS Archive Automatic Signing Key (2017) <qgis-developer@lists.osgeo.org>
[...]
W: Une erreur s'est produite lors du contrôle de la signature. Le dépôt n'est pas mis à jour et les fichiers d'index précédents seront utilisés. Erreur de GPG : https://qgis.org/ubuntu-ltr-2.18 cosmic InRelease : Les signatures suivantes ne sont pas valables : EXPKEYSIG CAEB3DC3BDF7FB45 QGIS Archive Automatic Signing Key (2017) <qgis-developer@lists.osgeo.org>
W: Impossible de récupérer https://qgis.org/ubuntu-ltr-2.18/dists/cosmic/InRelease Les signatures suivantes ne sont pas valables : EXPKEYSIG CAEB3DC3BDF7FB45 QGIS Archive Automatic Signing Key (2017) <qgis-developer@lists.osgeo.org>
W: Le téléchargement de quelques fichiers d'index a échoué, ils ont été ignorés, ou les anciens ont été utilisés à la place.
(sorry, it is in french, but it says that signatures are not valid, GPG error etc..).
Of course, installing the new key does NOT resolve the issue.
Please resign packages of 2.18 (and probably of some other packages, see #664 ).
It is very annoying for us because we still have some customers who are using 2.18.
The text was updated successfully, but these errors were encountered:
Since the expiration of the key qgis-2017.gpg.key, it is not possible anymore to install packages from ubuntu-ltr-2.18 or debian-ltr-2.18.
(sorry, it is in french, but it says that signatures are not valid, GPG error etc..).
Of course, installing the new key does NOT resolve the issue.
Please resign packages of 2.18 (and probably of some other packages, see #664 ).
It is very annoying for us because we still have some customers who are using 2.18.
The text was updated successfully, but these errors were encountered: