Control: tags -1 +wontfix Hi Fabian,
Quoting Fabian Grünbichler (2026-01-23 09:01:35) > you recently removed M-A:foreign from this package (which seems correct). > Instead of dropping it, please mark the package as M-A:same to allow > cross-builds that involve it in the dependency tree. [...] > I noticed this while investigating a fix for cross-builds involving cargo-c > which happened to involve reqwest as well, and thus regressed besides the > cargo-c issues because of the above. Given the prominence of reqwest it would > be great to get this fixed! Marking as M-A:foreign when reverse dependencies are M-A:same is wrong, so I removed that. M-A:same when package itself is arch-all is wrong too. I don't want to bloat the Debian archive and pressure the auto-builders with multiple identical copies, so I won't artificially mark the package as arch-all. What I find the correct goal here is for most possible packages to be marked arch-all and M-A:foreign, and a stepping stone to get there is to not do Multi-Arch marking at all until Arch marking is optimal. In short, I won't mark M-A:foreign because that would imply marking as arch-any, which I disagree with doing. Thanks for bringing it up, - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ * Sponsorship: https://ko-fi.com/drjones [x] quote me freely [ ] ask before reusing [ ] keep private
signature.asc
Description: signature
