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

APT Release key expired? #120

Open
pannal opened this issue Jan 4, 2020 · 4 comments
Open

APT Release key expired? #120

pannal opened this issue Jan 4, 2020 · 4 comments

Comments

@pannal
Copy link

pannal commented Jan 4, 2020

When trying to update my apt sources I get:

Err:17 https://swift.im/packages/debian/stretch release InRelease
  The following signatures were invalid: EXPKEYSIG 3A95CBB2E072AA5E Swift Package Maintainer <[email protected]>
Fetched 252 kB in 3s (78.6 kB/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
4 packages can be upgraded. Run 'apt list --upgradable' to see them.
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://swift.im/packages/debian/stretch release InRelease: The following signatures were invalid: EXPKEYSIG 3A95CBB2E072AA5E Swift Package Maintainer <[email protected]>
W: Failed to fetch https://swift.im/packages/debian/stretch/dists/release/InRelease  The following signatures were invalid: EXPKEYSIG 3A95CBB2E072AA5E Swift Package Maintainer <[email protected]>
W: Some index files failed to download. They have been ignored, or old ones used instead.

Trying to re-add the current key doesn't help.

Details:

pub   rsa4096 2015-11-11 [SC] [expired: 2019-11-28]
      0C4D 5A25 DBEF 212D 7E4F  BC4D 3A95 CBB2 E072 AA5E
uid           [ expired] Swift Package Maintainer <[email protected]>```
@theTaikun
Copy link

Likewise, trying to install swiften from debian repo and noticed the same thing.

@genbtc
Copy link

genbtc commented Jul 13, 2020

still expired.

@Kev
Copy link
Member

Kev commented Jul 13, 2020

Yep. It's still being worked on, thanks for the poke. (I think there's some trouble with working out how to cause reprepro to resign everything with the new key).

@coldtobi
Copy link

coldtobi commented Aug 5, 2022

Yep. It's still being worked on, thanks for the poke. (I think there's some trouble with working out how to cause reprepro to resign everything with the new key).

You do not need to have a new key, you can change the expiry of the old key.

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

5 participants