[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

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



On Tue, Sep 09, 2025 at 08:30:30AM +0200, Bjørn Mork wrote:
Daniel Baumann <daniel-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org> writes:

Luca: Given the impact of this and the feedback you got, did you
reconsider and are you going to do it and when are you going to do it,
or should I go forward and do it?

Why not? The deliberate delays imposed by bluca are still hurting Debian
users.

Apparently blucas feelings was so hurt by the this bug report that he
had to take a few days off, while more and more Debian stable systems go
offline around the world.

I propose that Debian drops bullet point 4 from the social contract.  It
looks like a bad joke at the moment.

Or maybe there is one DD out there with enough repsect for Debian users
to ignore the systemd maintainer bully?

The actual problem that we are facing that there is no possibility of undoing the point release short of doing another quick followup 13.2 or 13.1.1 point release to fix this. The broken systemd is in _stable_ with the old version gone, and security being the only possible way to get a new version on our users' systems without manual intervention.

Greetings
Marc

--
-----------------------------------------------------------------------------
Marc Haber         | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany    |  lose things."    Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421


Reply to: