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

Proposed keyserver changed to functional one #992

Merged
merged 1 commit into from
Nov 2, 2021
Merged

Proposed keyserver changed to functional one #992

merged 1 commit into from
Nov 2, 2021

Conversation

Vitexus
Copy link
Contributor

@Vitexus Vitexus commented Oct 27, 2021

Fixes #990 - the not so much experienced users are confused by cryptic error message

Requirements

This is only minor change. No extra requrements

Description of the Change

The current example uses pool.sks-keyservers.net that is no longer operating. The new one is working well:

repo@apt:~/bin$ gpg --no-default-keyring --keyring trustedkeys.gpg --keyserver pool.sks-keyservers.net --recv-keys CE1A3DD5E3C94F49
gpg: keyserver receive failed: No name
repo@apt:~/bin$ 
repo@apt:~/bin$ gpg --no-default-keyring --keyring trustedkeys.gpg --keyserver keyserver.ubuntu.com --recv-keys CE1A3DD5E3C94F49
gpg: key CE1A3DD5E3C94F49: public key "MariaDB Enterprise Signing Key <[email protected]>" imported
gpg: Total number processed: 1
gpg:               imported: 1

@lbolla lbolla merged commit 174943c into aptly-dev:master Nov 2, 2021
@lbolla
Copy link
Contributor

lbolla commented Nov 2, 2021

Thanks!

@randombenj randombenj added this to the 1.5.0 milestone Jun 23, 2022
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 this pull request may close these issues.

apt-key returns 'No name'
3 participants