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-key returns 'No name' #990

Closed
jkorinth opened this issue Oct 22, 2021 · 4 comments · Fixed by #992
Closed

apt-key returns 'No name' #990

jkorinth opened this issue Oct 22, 2021 · 4 comments · Fixed by #992

Comments

@jkorinth
Copy link

The key for the aptly repo can no longer be obtained:

apt-key adv --keyserver pool.sks-keyservers.net --recv-keys ED75B5A4483DA07C
Executing: /tmp/apt-key-gpghome.o3YoaNAhy8/gpg.1.sh --keyserver pool.sks-keyservers.net --recv-keys ED75B5A4483DA07C
gpg: keyserver receive failed: No name

This breaks Armbian docker-based build scripts.

@r4co0n
Copy link

r4co0n commented Oct 25, 2021

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 keys.gnupg.net equally applies to pool.sks-keyservers.net, as the prior was just forwarding to the latter, from what I can tell. (I don't have access to historical DNS records.)

@jkorinth
Copy link
Author

Thanks for the explanation! I wrongly assumed the key had expired or something along those lines.

@jdbarnes-isi
Copy link

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

lbolla added a commit to aptly-dev/www.aptly.info that referenced this issue Dec 16, 2021
@lbolla
Copy link
Contributor

lbolla commented Dec 16, 2021

Fixed in aptly-dev/www.aptly.info@da6731c

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

Successfully merging a pull request may close this issue.

4 participants