Hi, This type of bug is a natural artifact of the way rust crates are structured and updated, and the Rust team is continually aware of these types of bugs. There is no need to file these types of bugs for packages in unstable as the testing migration script will prevent migrations anyway, rendering a RC bug report unbeneficial and contributing to more paperwork for the packaging team.
Best, Ximin Paul Gevers: > Source: rust-cargo > Version: 0.37.0-1 > Severity: serious > Tags: ftbfs sid bullseye > Justification: ftbfs > > Dear maintainers, > > Your package Build-Depends on librust-crates-io-0.25+default-dev but that > package doesn't exist. > > Paul > > -- System Information: > Debian Release: bullseye/sid > APT prefers testing > APT policy: (990, 'testing'), (500, 'testing-debug') > Architecture: amd64 (x86_64) > > Kernel: Linux 5.3.0-2-amd64 (SMP w/2 CPU cores) > Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, > TAINT_UNSIGNED_MODULE > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), > LANGUAGE=en_US:en (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > > -- GPG: ed25519/56034877E1F87C35 GPG: rsa4096/1318EFAC5FBBDBCE https://github.com/infinity0/pubkeys.git