Repository navigation
openssl is fetched from the release files its download page links - #168
Merged
Merged
Conversation
…, not through www.openssl.org's redirect to them, which answered a runner 500 four times
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
www.openssl.org/source/ is a 301 to the project's GitHub release file, and that redirector answered HTTP 500 four times to main's CI job for 52682fc while the release file itself was there. openssl-library.org's source page links the GitHub release files directly, tarball and .asc; the manifest now names that address. Same file name, so sources.lock and the signature check are unchanged; the currency rule is keyed by name, not by URL.