On Tue, Nov 10, 2026 at 09:59:26PM +0200, Edmund Lodewijks wrote:
(b) A maintainer binary upload. I (or the sponsor) build(s) the binaries locally against the bootstrap compiler, and a sponsor uploads those rather than just signing a .dsc.Between those options, I lean towards option (a). Against option (b), rust's README.source puts it quite nicely into words:"[The traditional Debian way is that] a developer locally installs some upstream bootstrapping binaries [and] builds a Debian package, using these binaries as undeclared build dependencies. [...] The problem with this is, Debian does nothave any policy nor infrastructure that can try to reproduce what this developer supposedly did."
(it's indeed a traditional way, and it's also indeed not ideal)
2. Is an amd64-only first upload acceptable?
Even having leaf package on just one architecture for significant amount of time is permissible, even more so if you are going to bootstrap other architectures later.
2. debian/copyright is not finished (barely started). The bundled mingw-w64, wasi-libc, BSD libc and aro trees still need auditing. I would appreciate guidance from anyone who has done this at scale (Rust, Go, npm?). There are ~30,000 files in the tarball, and from what I can see, there will be a variety of licenses. Perhaps there are tools available to extract this information? Thank you in advance!
Consider repacking to remove stuff you won't use (assuming not everything there is needed on Debian).
at any point. My chain takes around 1.5 to 2 hours on 8 cores, which may or may not be out of reach for a buildd.
This is much less than what do many packages take on amd64 buildds. -- WBR, wRAR
signature.asc
Description: PGP signature

