On Tue, Jul 21, 2026, at 6:18 PM, Adrian Bunk wrote: > On Tue, Jul 21, 2026 at 04:45:28PM +0200, Fabian Grünbichler wrote: >> On Tue, Jul 21, 2026, at 1:11 AM, Adrian Bunk wrote: >> > Apparently the old ftp team considered it DFSG-compliant to include >> > binaries downloaded from the internet[1] and execute these binaries >> > on our trusted buildds. >> > >> > It would be good to hear from the new DFSG team whether this is still >> > considered to fully comply with the Debian Free Software Guidelines. >> >> one of the reasons I started doing proper backports for Trixie was that >> BPO admins were not okay with doing that kind of jumps/rebootstraps. > > That makes sense, and I do also not see how an upload to stable > (or security) with sourceless binaries would be permitted without > a 3:1 majority in a GR granting an exception.
just FTR/for the avoidance of doubt - I've never used the dlstage0 build profile for uploads to the archive (I have used it from time to time locally when I got reports that it broke, to debug and fix it). I think this is mostly integration work at this point - I am committed to keeping trixie-backports current at least until forky becomes stable, and integrating cross builds (either on the upstream level or on the package level[0]) should fill the gaps for bookworm and or after that point. the toolchain itself should also be reproducible (the documentation isn't atm). 0: http://crossqa.debian.net/src/rustc looks mostly okay ;)
