-
-
Notifications
You must be signed in to change notification settings - Fork 372
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 used to sign aptly releases has expired #364
Comments
I'm getting this too, the key has expired http://keys.gnupg.net/pks/lookup?search=0x2A194991&op=vindex |
sorry for the trouble, I'm going to update the key tomorrow morning |
New key uploaded: https://groups.google.com/d/msg/aptly-discuss/Ny2NIqDgjHU/ZI6aNBeEAwAJ |
alext
referenced
this issue
in alphagov/puppet-aptly
Mar 15, 2016
The previous one has expired and been replaced. See https://github.com/smira/aptly/issues/364 for details.
GregSutcliffe
referenced
this issue
in GregSutcliffe/puppet-aptly
May 7, 2016
The previous one has expired and been replaced. See https://github.com/smira/aptly/issues/364 for details.
stevie-
referenced
this issue
in researchgate/puppet-aptly
Sep 15, 2016
The previous one has expired and been replaced. See https://github.com/smira/aptly/issues/364 for details.
Key has expired again!
|
Getting this addressed, sorry #717 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The gpg key used to sign aptly releases appears to have expired:
This causes problems when trying to
apt-get update
:The text was updated successfully, but these errors were encountered: