Bug#1112535: /usr/lib/systemd/systemd-networkd: segfault after upgrade to 257.8-1~deb13u1, no connectivity after reboot

[Adam D. Barratt]

On Sun, 2025-09-07 at 23:05 -0400, Kevin Otte wrote:
> 
[...]
> > On Sun, 07 Sep 2025 23:02:13 +0100 "Adam D. Barratt"
> > <adam at adam-barratt.org.uk> wrote:
> > > On Sun, 2025-09-07 at 22:52 +0100, Tim Small wrote:
> > > > This was reported a good week before Debian 13.1 went out, so
> > > > I'm a
> > > > bit surprised it still went into that?
> > > 
> > > It was reported at a non release critical severity, tagged
> > > "moreinfo"
> > > and neither the submitter nor the maintainer (nor anyone else)
> > > raised
> > > it to the Release Team's attention.
> 
> And why is that? It was filed against proposed-updates. I thought the
> whole point of that mechanism was to test the proposed update and 
> withdraw it if problems were found, avoiding this very scenario. The 
> process clearly broke down here.

In fact, the bug was filed against the version of the package that was
in stable at the time, not the newer version in proposed-updates.

The 13.1 point release contained updates to 80 packages. The 12.12
point release that happened on the same day had more than twice that.
There's no way the Release Team can be expected to monitor every bug of
any severity that might be filed or updated on all of those packages,
particularly when those bugs aren't even filed against the newer
version.

This is why the mails announcing the upcoming point release on debian-
stable-announce request that the debian-release list be copied on any
bugs relevant to packages in proposed-updates.

Regards,

Adam