-
-
Notifications
You must be signed in to change notification settings - Fork 376
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-key returns 'No name' #990
Comments
Please see https://stackoverflow.com/questions/66217436/gpg-keyserver-receive-failed-no-name . This is a general issue with GPG and not related to aptly per se. Relevant documentation and/or scripts should be updated, please refer to the specific places where aptly got it wrong. EDIT: Please note that stuff concerning |
Thanks for the explanation! I wrongly assumed the key had expired or something along those lines. |
http://repo.aptly.info/ shows pre-commit server message, so this continues to be an issue until that commit is released or someone manually updates the page. @lbolla @Vitexus |
Fixed in aptly-dev/www.aptly.info@da6731c |
The key for the aptly repo can no longer be obtained:
This breaks Armbian docker-based build scripts.
The text was updated successfully, but these errors were encountered: