Deal with distfile requests being blocked by crates.io#4052
Merged
Conversation
crates.io (on Amazon CloudFront) is now rejecting our requests with 403. I have made a similar change to upstream Portage, but let's use our own string for Flatcar. Signed-off-by: James Le Cuirot <jlecuirot@microsoft.com>
This hasn't actually been merged upstream yet, but it's about to be. The user-agent change deals with the blocked requests, but it turns out we should be using this faster and less restricted endpoint anyway. Signed-off-by: James Le Cuirot <jlecuirot@microsoft.com>
Member
|
lgtm, i guess we should just make sure that the build goes thru and all good then |
Contributor
Author
The relevant bit has passed. All the packages are built as binaries, so there are no more distfiles to download. If any of them had mismatched, it would have failed the hash checks. |
Member
Perfect then! |
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
2 participants
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.
crates.io (on Amazon CloudFront) is now rejecting our requests with 403. This can be avoided by setting a custom user-agent for wget. I have made a similar change to upstream Portage, but let's use our own string for Flatcar.
While the user-agent change deals with the blocked requests, it turns out we should be using a different faster and less restricted endpoint anyway, so let's also take the (about to be merged upstream) cargo.eclass change as well.
How to use
Try building a Rust-based package with
GENTOO_MIRRORS="".Testing done
Jenkins got as far as the image job, which failed for an unrelated reason.
changelog/directory (user-facing change, bug fix, security fix, update)/bootand/usrsize, packages, list files for any missing binaries, kernel modules, config files, kernel modules, etc.