ros2_rust: Rust Minimal Workflow Failing
Our latest Rust Minimal workflow failed with the following.
Starting >>> rclrs
--- output: rclrs
error: package `home v0.5.11` cannot be built because it requires rustc 1.81 or newer, while the currently active rustc version is 1.75.0
Either upgrade to rustc 1.81 or newer, or use
cargo update home@0.5.11 --precise ver
where `ver` is the latest version of `home` supporting rustc 1.75.0
---
--- stderr: rclrs
error: package `home v0.5.11` cannot be built because it requires rustc 1.81 or newer, while the currently active rustc version is 1.75.0
Either upgrade to rustc 1.81 or newer, or use
cargo update home@0.5.11 --precise ver
where `ver` is the latest version of `home` supporting rustc 1.75.0
---
Failed <<< rclrs [1.32s, exited with code 1]
Changelog for home can be found here
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 16
which7.0.1 is now released which should resolve this problem.@Xaeroxe thanks for your feedback, we’ve instead opted to bump the version of
bindgento 0.70, which droppedwhichas a dependencyTruthfully I suspect it’s a very very small portion of the community that would want to explicitly support both a frozen compiler version and the latest stable compiler at the same time. Those who want to support a frozen compiler version will most likely want all their dependencies to be frozen, so they’ll just use a lockfile and/or their own crate registry for all their dependencies.
I just tested out my lockfile idea with #450 but it failed. It looks like colcon-cargo might not give any regard to the lockfile in the source code, but I’d need to do more local experimentation to figure out if that’s the actual problem.
I also attempted a different solution where we would use
$ cargo add home@=0.5.9inside the CI workflow script for Minimal. That should have the effect that @esteve 's suggestion is achieving but applied only to the Minimal CI workflow, with no impact on downstream users. Somehow that is also failing.There must be something that I don’t understand about how
ros-tooling/action-ros-ciworks, because somehow even directly modifying theCargo.tomlofrclrsusingcargo addisn’t stoppingcolcon-cargofrom using version 0.5.9 ofhome, even though the same exact steps work when I try them locally on my own computer.It’s very late for me now, so I’ll try revisiting this tomorrow.