On Tue, Nov 25, 2025 at 01:46:04PM -0800, Josh Triplett wrote: >... > Packages of the Rust standard library (`std`) don't care what the host > is; they *only* care what the target is. They could reasonably be either > `librust-std-dev-targetname:all` or `librust-std-dev:targetname`; either > one works, it's just that the latter requires the architecture to be > enabled on the system in order to depend on it. >...
`librust-std-dev:targetname` does not work in Debian unless targetname is the host architecture. And when targetname is not a Debian release architecture, then that's really far outside of what could work. The options available are `librust-std-dev-targetname:all` or `librust-std-dev-targetname:host`. Security does not seem to be a high priority for proponents of more Rust in Debian, but when that gets sorted out then :all would currently still exclude the package from proper security support due to lack of binNMUs for :all. What works and might realistically be security-supported in Debian 14 is `librust-std-dev-targetname:host`. >From maintainer and user point of views `librust-std-dev-targetname:all` and `librust-std-dev-targetname:host` are nearly identical, so that's not a big issue. cu Adrian
