Control: severity -1 criticial
On 2026-01-19 13:16:37 +0100, Matthias Klose wrote:
> Control: tags -1 + important
>
> On 1/19/26 12:42, Christian Marillat wrote:
> > On 19 janv. 2026 12:06, Matthias Klose <[email protected]> wrote:
> >
> > > On 1/19/26 11:54, Christian Marillat wrote:
> > > > Package: binutils-x86-64-linux-gnu
> > > > Version: 2.45.50.20260119-1
> > > > Severity: serious
> > > > Dear Maintainer,
> > > > I see this issue on amd64, i386 arm64 and with various sources.
> > >
> > > please submit complete bug reports. "various" ...
> >
> > Various can be replaced by all.
> >
> > This output come-from svt-av1 dmo source
> >
> > https://www.deb-multimedia.org/pool/main/s/svt-av1-dmo/svt-av1-dmo_3.1.2-dmo1.debian.tar.xz
> > https://www.deb-multimedia.org/pool/main/s/svt-av1-dmo/svt-av1-dmo_3.1.2-dmo1.dsc
> > https://www.deb-multimedia.org/pool/main/s/svt-av1-dmo/svt-av1-dmo_3.1.2.orig.tar.xz
>
> that's outside of Debian. Is this seen in the Debian archive as well? Note,
> that you should just rebuild your binaries that have sframe v2 sections.
This breaks compiling the simplests of programs:
$ cat test.c
int main() {}
$ gcc test.c
/usr/bin/x86_64-linux-gnu-ld.bfd: input SFrame sections with different format
versions prevent .sframe generation
/usr/bin/x86_64-linux-gnu-ld.bfd: final link failed
collect2: error: ld returned 1 exit status
$ apt-cache policy binutils
binutils:
Installed: 2.45.50.20260119-1
Candidate: 2.45.50.20260119-1
Version table:
*** 2.45.50.20260119-1 500
500 http://localhost:3142/debian-buildd buildd-unstable/main amd64
Packages
100 /var/lib/dpkg/status
2.45.50.20251209-1+b1 500
500 http://localhost:3142/debian unstable/main amd64 Packages
So this very much affects Debian. We are just lucky that the buildd
chroots haven't been regenerated yet.
Dear wb-admins, please stop the regeneration of the buildd chroots.
Cheers
--
Sebastian Ramacher
