On Tue, Jul 21, 2026, at 1:11 AM, Adrian Bunk wrote: > On Mon, Jul 20, 2026 at 05:29:15PM -0400, Andres Salomon wrote: >> >> >> On 7/20/26 17:17, Fabian Grünbichler wrote: >> > On Mon, Jul 20, 2026, at 11:08 PM, Sebastian Andrzej Siewior wrote: >> > > Hi, >> > > >> > > I've been preparing clamav upload for stable and noticed that one of its >> > > rust bits requires rustc 1.87.0. There was once rust-web but this is >> > > gone now. >> > > I could try to downgrade it but there was a bug against an earlier >> > > version where it failed to read (some) .tiff files and fix was a newer >> > > rust component for it. Wouldn't be surprised if something similar did >> > > happen for jpeg, too (the package asking for newer rustc is zune-jpeg). >> > > >> > > The NEWS file for 1.4.4 mentiones rustc 1.87 as the minimum. >> > > >> > > I guess the only way forward is via -bpo? >> > >> > I think it is just a matter of time before rustc-web has to be >> > reintroduced for Trixie (via chromium/firefox-esr) - AFAIK Andres (CCed) >> > is already working on preparing it(s prerequisites). >> >> I'm hoping Emilio will handle rustc-web. I'm handling the llvm-toolchain-22 >> backport (which newer rust depends upon), but I keep hitting issues. I'm >> hoping to get that in before the next chromium early release in a week, >> though. > > It would be good to bootstrap rustc-web/trixie from rustc/trixie-backports. > If help is needed with that, I'd be willing to help.
see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1126584 for some discussion/background. help with implementing it would be appreciated - my Rust packaging related TODO list is fairly long atm unfortunately. > 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.
