You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When publishing the xdp crate, I get the following error:
ubuntu@:~/s2n-quic$ cargo publish --manifest-path tools/xdp/s2n-quic-xdp/Cargo.toml -p s2n-quic-xdp
Updating crates.io index
Packaging s2n-quic-xdp v0.52.0 (/home/ubuntu/s2n-quic/tools/xdp/s2n-quic-xdp)
Verifying s2n-quic-xdp v0.52.0 (/home/ubuntu/s2n-quic/tools/xdp/s2n-quic-xdp)
Updating crates.io index
error: failed to verify package tarball
Caused by:
package `aya v0.13.1` cannot be built because it requires rustc 1.80.0 or newer, while the currently active rustc version is 1.74.1
This is because we set the publish version to use 1.80.0 rustc version:
Upgrade MSRV to 1.80.0. This was overriding the rustc version used when publishing:
ubuntu@:~/s2n-quic$ rustup default 1.80.0
info: using existing install for '1.80.0-x86_64-unknown-linux-gnu'
info: default toolchain set to '1.80.0-x86_64-unknown-linux-gnu'
1.80.0-x86_64-unknown-linux-gnu unchanged - rustc 1.80.0 (051478957 2024-07-21)
info: note that the toolchain '1.74.1-x86_64-unknown-linux-gnu' is currently in use (overridden by '/home/ubuntu/s2n-quic/rust-toolchain')
Upgrading MSRV to 1.80.0 also allows us to resolve #2334
Requirements / Acceptance Criteria:
Out of scope:
The text was updated successfully, but these errors were encountered:
jouho
changed the title
publishing s2n-quic-xdp crate fails due to MSRV
Publishing s2n-quic-xdp crate fails due to MSRV
Jan 8, 2025
Problem:
When publishing the xdp crate, I get the following error:
This is because we set the publish version to use 1.80.0 rustc version:
s2n-quic/tools/xdp/rust-toolchain
Line 2 in 2f357d5
Solution:
Upgrade MSRV to 1.80.0. This was overriding the rustc version used when publishing:
Upgrading MSRV to 1.80.0 also allows us to resolve #2334
Requirements / Acceptance Criteria:
Out of scope:
The text was updated successfully, but these errors were encountered: