On 05/08/2024 21:56, Jonas Smedegaard wrote:
> It seems that
> at https://ci.debian.net/packages/r/rust-async-mutex/testing/riscv64/49981801/ something makes the tests depend on a bogus package
> "async-std" (notice the lack of leading "librust-" and trailing "-dev".) Or
> am I misreading those error messages and they are mean "crate" when they say
> "package"?
>
> Perhaps that's a clue to what concrete goes wrong?
293s debian cargo wrapper: running subprocess (['env', 'RUST_BACKTRACE=1', '/usr/bin/cargo', '-Zavoid-dev-deps', 'test', '--verbose', '--verbose', '-j4', '--target', 'riscv64gc-unknown-linux-gnu', '--all-targets', '--all-features'],) {}
294s error: no matching package named `async-std` found
294s location searched: registry `crates-io`
294s required by package `async-mutex v1.4.0 (/usr/share/cargo/registry/async-mutex-1.4.0)`
Message produced by cargo. Somehow confusing, yes.
async-mutex dev-depends on async-std, so it's in the Depends of d/tests/control:
Depends: dh-cargo (>= 18), librust-async-std-1+default-dev (>= 1.12-~~), [...]
However interesting is that autopkgtest didn't install it, seen in the debci
log.
--
Sdrager,
Blair Noctis
Attachment:
pgpEACxYC7ntT.pgp
Description: OpenPGP digital signature