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.
Status
Ready for review
Description of Changes
First, adjust how Rust is installed in the builder container
Install Rust and rustup in slightly more straightforward directories and
unconditionally add it to $PATH instead of weirdly in /root/.cargo.
This setup is partially based on rust-lang/rustup#1085 (comment),
which is described as unsupported for multiple users but our containers
are single-user.
The plan is to copy this to the development container as well.
Second, and primarily, update Rust in builder to 1.69.0
For the Sequoia work, we're planning to use 1.69.0 so we need to update
the builder to match. This is being done separately since it already
affects a production component (the cryptography wheel) and should be
tested independently.
This also lets us get rid of our index-warming hack since we can use the
new fast sparse protocol instead
(https://blog.rust-lang.org/2023/03/09/Rust-1.68.0.html#cargos-sparse-protocol).
Refs #6817.
Testing
How should the reviewer test this PR?
(AFAIK that's the main place we use cryptography on the server)
Deployment
Any special considerations for deployment? No.
Checklist