Source: rust-sha256
Version: 1.6.0-5
Severity: normal
X-Debbugs-Cc: [email protected], [email protected]

hi!

I noticed you started packaging some Rust crates (I assume for forgejo?), but
deviate from the Rust packaging policy while using dh-cargo. this bug is just
an example, I assume you probably know which other packages follow this scheme
;)

in order to support cross building, librust-*-dev packages currently need to be
Architecture:any and M-A:same. while some packages can be marked
Architecture:all instead, this is not a given (and can change if any of its
dependencies later change), the "safe" fall back is M-A:same combined with
Architecture:any. this also applies to the "empty" feature packages (which we
usually omit nowadays, because ftp-masters frowned upon them).

while this does waste some archive space (and we do hope to sort this out at
some point), it is the compromise that dpkg devs, Helmut and the Rust team
agreed upon in order to avoid breaking all cross builds involving Rust.

it would be great if you could reconsider!

Fabian

Reply via email to