Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GPG key of Debian repo has expired again #455

Closed
nroach44 opened this issue Mar 6, 2024 · 2 comments
Closed

GPG key of Debian repo has expired again #455

nroach44 opened this issue Mar 6, 2024 · 2 comments

Comments

@nroach44
Copy link

nroach44 commented Mar 6, 2024

General informations

Operating system : Debian 12

Problem's description

Err:7 http://deb.ocsinventory-ng.org/debian bullseye InRelease
  The following signatures were invalid: EXPKEYSIG 8D1DA07AF0AF3862 Gilles DUBOIS <gilles.dubois@factorfx.com>
Fetched 1,671 B in 2s (827 B/s)                                                        
Reading package lists... Done
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://deb.ocsinventory-ng.org/debian bullseye InRelease: The following signatures were invalid: EXPKEYSIG 8D1DA07AF0AF3862 Gilles DUBOIS <gilles.dubois@factorfx.com>
W: Failed to fetch http://deb.ocsinventory-ng.org/debian/dists/bullseye/InRelease  The following signatures were invalid: EXPKEYSIG 8D1DA07AF0AF3862 Gilles DUBOIS <gilles.dubois@factorfx.com>
W: Some index files failed to download. They have been ignored, or old ones used instead.
@nroach44 nroach44 changed the title GPG key of Debain repo has expired again GPG key of Debian repo has expired again Mar 6, 2024
@Lea9250
Copy link
Contributor

Lea9250 commented Mar 6, 2024

Hi @nroach44,

Is it possible that you didn't re import the key since it expired last time ? See : https://wiki.ocsinventory-ng.org/03.Basic-documentation/Setting-up-a-OCS-Inventory-Server-with-rpm/#install-ocs-inventory-server-with-apt

Best regards,
Léa

@nroach44
Copy link
Author

Yup, looks like you're right - this was a server that definitely should have been caught by the fix up scripts, but somehow was missed.

Sorry for that!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants