Hi Max,
> rustc-1.91 has a Noble backport and the bug does not exist
in the 1.91 toolchain.
I tried using rustc-1.91 today. While its cargo wrapper does execute the
correct cargo binary in a standard environment now, it seems like it
still executes `/usr/bin/cargo` when preparing the environment as
described in its usage message (i.e. when using it to build a Rust crate
as part of a Debian package build):
export PATH=/path/to/dir/of/this/script:$PATH
export CARGO_HOME=debian/cargo_home
cargo prepare-debian /path/to/local/registry [--link-from-system]
cargo build
[...]
I added some debug output to the override_dh_auto_build target in our
debian/rules and I get the following output on Noble:
echo "Building NSS library with $$(which cargo) ($$(cargo --version))"
Building NSS library with /usr/lib/rust-1.91/share/cargo/bin/cargo (cargo
1.75.0)
A quick look at /usr/lib/rust-1.91/share/cargo/bin/cargo shows that it
does indeed still hardcode /usr/bin/cargo in a few places:
$ grep /usr/bin/cargo /usr/lib/rust-1.91/share/cargo/bin/cargo
"/usr/bin/cargo"] + list(args) +
logrun(["env", "RUST_BACKTRACE=1", "/usr/bin/cargo"] + list(newargs),
check=True)
return logrun(["env", "RUST_BACKTRACE=1", "/usr/bin/cargo"] +
list(newargs)).returncode
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2100266
Title:
Versioned cargo wrapper script points to default cargo
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rustc-1.76/+bug/2100266/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
