On Sun, Aug 09, 2026 at 09:20:08PM +0300, Adrian Bunk wrote: > On Thu, Aug 06, 2026 at 04:56:52PM +0200, Santiago Vila wrote: > > Hello. > > Hi Santiago, > > > The size of the unstable chroot has grown a lot lately: > > > > -rw-r--r-- 1 root root 157858150 ago 6 14:43 bookworm.tar.gz > > -rw-r--r-- 1 root root 161658038 ago 6 14:44 trixie.tar.gz > > -rw-r--r-- 1 root root 169416889 ago 6 14:44 forky.tar.gz > > -rw-r--r-- 1 root root 445400544 ago 6 14:45 sid.tar.gz > > > > I doubt this is suitable for release and I wish you could report > > it properly to whatever package is appropriate. > > $ tar tvf sid_amd64.tar.gz | sort -g -k3 > ... > -rwxr-xr-x root/root 245063984 2026-07-19 11:28 > ./usr/libexec/gcc/x86_64-linux-gnu/16/lto1 > -rwxr-xr-x root/root 251649632 2026-07-19 11:28 > ./usr/libexec/gcc/x86_64-linux-gnu/16/cc1 > -rwxr-xr-x root/root 267410352 2026-07-19 11:28 > ./usr/libexec/gcc/x86_64-linux-gnu/16/cc1plus > $ > > This might have been #1143542 (which is fixed in the latest gcc-16 upload).
No, this is not fixed in the latest upload. Just take a look at the equivalent arm64 files in the last build log for arm64: https://buildd.debian.org/status/fetch.php?pkg=gcc-16&arch=arm64&ver=16.2.0-1&stamp=1786287257&raw=0 (Even if it's a different architecture, the size is usually similar and enough to tell that this is still not fixed). I would report this myself but I think it would be much better if the WB team could care about this sort of thing. Thanks.
