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

keyserver default url fails with apt #331

Closed
schorsch opened this issue Aug 13, 2015 · 4 comments
Closed

keyserver default url fails with apt #331

schorsch opened this issue Aug 13, 2015 · 4 comments

Comments

@schorsch
Copy link

github.com/opscode-cookbooks/apt expects a keyserver without leading hkp: and trailing port:

Executing: gpg --ignore-time-conflict --no-options --no-default-keyring --homedir /tmp/tmp.RDomMv27we --no-auto-check-trustdb --trust-model always --keyring /etc/apt/trusted.gpg --primary-keyring /etc/apt/trusted.gpg --keyserver hkp://hkp://keys.gnupg.net:80:80 --recv some-key

so keys.gnupg.net is enough in
default["percona"]["apt"]["keyserver"] = "hkp://keys.gnupg.net:80"
default["percona"]["apt"]["keyserver"] = "keys.gnupg.net"

@schorsch
Copy link
Author

also had a problem with the apt key on ubuntu:
default["percona"]["apt"]["key"] = "0x1C4CBDCDCD2EFD2A"
it works without 0x
default["percona"]["apt"]["key"] = "1C4CBDCDCD2EFD2A"

@jharley
Copy link

jharley commented Aug 21, 2015

Confirmed.

This change was made to the upstream cookbook with this commit and will cause this regression if you haven't pegged 'apt' to something less than 2.8 (e.g. "~> 2.7.0").

@xorima
Copy link
Contributor

xorima commented May 11, 2019

Closing due to inactivity.

If this is still an issue please reopen or open another issue. Alternatively drop by the #sous-chefs channel on the Chef Community Slack and we'll be happy to help!

Thanks,
Sous-Chefs

@xorima xorima closed this as completed May 11, 2019
@lock
Copy link

lock bot commented May 20, 2020

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators May 20, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants