Update to Rust 1.73.0:
See the blog post and release notes for more details.
Updates may require up to 24 hours to propagate to mirrors. If the following command doesn't work, please retry later:
sudo dnf upgrade --refresh --advisory=FEDORA-2023-e29b93e24d
Please log in to add feedback.
0 | 4 | Test Case rust compile |
This update has been submitted for testing by jistone.
This update's test gating status has been changed to 'ignored'.
This update has been pushed to testing.
This update's test gating status has been changed to 'passed'.
This broke the Fedora Asahi kernel build (which uses unstable features). We normally fix things when changes are required, since unstable features change all the time, but this time it looks like a compiler bug (per discussion in #rust:fedoraproject.org).
In particular, this used to compile on 1.72.1 (with
RUSTC_BOOTSTRAP=1
), and now doesn't: https://play.rust-lang.org/?version=nightly&mode=debug&edition=2021&gist=34b8d13b298f3cf711e08433eb04d2e3If there is some way to fix that code to make it work in 1.73.0 (while keeping the constness of
IdArray::new
) then we'll make the change, but otherwise we're stuck.Bodhi is disabling automatic push to stable due to negative karma. The maintainer may push manually if they determine that the issue is not severe.
Rust 1.73.0 breaks Firefox 118 builds (and presumably lower) by way of missing (unstable?) platform-specific SIMD intrinsics on, at the very least, arm64.
Confirm local breakage for me too
Changes to unstable features are not compiler bugs, unless they indirectly affect stable code (e.g. exposed by stable std functionality). In particular,
const Trait
is undergoing heavy revision lately, so I'm not surprised such code broke.For Asahi, I suggest you use a side tag to build using a version you can deal with, until you can figure out how to work with the current stable. But I firmly do not want to block Fedora's toolchain on unstable feature usage.
For Firefox, I see that
firefox-118.0.1-7.fc40
built fine withrust-1.73.0-1.fc40
. If your own build is enabling unstable features, then I'm afraid that's not supported either.@ngompa is your local breakage something different?
Works fine for me.
There were some issues with conflicting
<number>::div_ceil
implementations (with thenum::Integer
trait that has a slightly different API for the function of the same name) due to this API being stabilized in Rust 1.73, but I already fixed all (two) affected packages in Fedora.This update can be pushed to stable now if the maintainer wishes
This update has been submitted for stable by jistone.
There is an ongoing freeze; this will be pushed to stable after the freeze is over.
This update has been pushed to stable.