-
Notifications
You must be signed in to change notification settings - Fork 2k
Switch to p80.pool.sks-keyservers.net to ensure port 80 #622
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
Conversation
The PR looks good, but the failing legs still seem to be hitting some different GPG errors, I don't see the |
Hmm. From one of the file alpine image builds
It's not clear which gpg sever it's failing on, or if it's all of them. |
Doing some testing, this fails on Alpine for some reason:
|
maybe related to this one: #380 |
@chorrell i confirm that it works:
|
Hmm, maybe. So if we switch to using |
Maybe related: https://dev.gnupg.org/T2990#98557 |
I just pushed a commit to switch to Maybe we should update the list of gpg servers to try p80 and ipv4?:
|
@chorrell it should do the job, as it seems to be quite random now the dns resolution. |
Yeah, exactly. I make that change later tonight and update this PR |
Another trick can be installing gnupg from edge:
Which contains this fix: https://dev.gnupg.org/rG15d2a009931f44a60b9df6325f837add208459d6 |
No, just random responses as well:
|
It is quite unpredictable now,@chorrell trying both p80 and ipv4 it's more than 👍 to me |
I'm thinking we close this in favour of #623 |
This fixes an issue noted in PR #621 and #567 (comment)