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 seems to be the wrong one #3858

Closed
rrthomas opened this issue May 19, 2023 · 5 comments
Closed

GPG key seems to be the wrong one #3858

rrthomas opened this issue May 19, 2023 · 5 comments
Labels
bug Something isn't working

Comments

@rrthomas
Copy link
Contributor

Describe the bug
Having downloaded the PGP key block xpra.asc file as instructed for Debian-based distros (Ubuntu 22.04 in my case), I get:

W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://xpra.org jammy InRelease: The following signatures were invalid: EXPKEYSIG 18ADB31CF18AD6BB Antoine Martin <[email protected]>
W: Failed to fetch https://xpra.org/dists/jammy/InRelease  The following signatures were invalid: EXPKEYSIG 18ADB31CF18AD6BB Antoine Martin <[email protected]>

Additional context
What is odd is that when I had this problem some weeks ago on another machine, I downloaded the file again and got a newer one (datestamp March 24th 2022). This appears to be the right one, as it contains the key referred to, whereas the file currently available does not.

@rrthomas rrthomas added the bug Something isn't working label May 19, 2023
@totaam
Copy link
Collaborator

totaam commented May 21, 2023

Does this solve things: #3846 (comment)

@rrthomas
Copy link
Contributor Author

@totaam: thanks, the key seems to have been updated once more; did you do something? What I was trying to explain above is that when I downloaded the key about two weeks ago, I got the same key as now. But when I downloaded it two days ago, I got an older key.

@totaam
Copy link
Collaborator

totaam commented May 22, 2023

@rrthomas perhaps this answers your question?
#3846 (comment)

@rrthomas
Copy link
Contributor Author

Ah yes, thanks! So that means that the key has been updated, and this issue can be closed?

@totaam
Copy link
Collaborator

totaam commented May 22, 2023

Different distribution releases require different keys.. so I have tried not to update existing files and change URLs to new ones instead, in the (perhaps foolish) hope that this would not break existing workflows.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants