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

[Adrien CLERC]

On Mon, 8 Sep 2025 21:49:09 +0100 Luca Boccassi <bluca at debian.org> wrote:
 >
 > "highly impactful" is in the eye of the beholder.

Could you please stop this? We already told you multiple times that 
users that are not you are important, and you ignored them. As a 
reference, see sysctl.conf case in 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1110184 that you never 
mentionned in NEWS, even if the initial bug report was 1 year old 
(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1077184) and never 
closed. And it did exactly the same thing as this bug, aka broke 
networking for users. In the case of sysctl.conf, it was upgrading from 
an old and deprecated configuration (sorry for using Debian since before 
first release of systemd and even pulseaudio).
Here, we are facing multiple users carefully raising an alarm before the 
package is even pushed to more users, and you just say that: "Sorry, I 
don't care about you".

When you have such a configuration, it's usually on a headless machine. 
Broking network is nearly the worst thing you can do on it. It's 
important. We can completely understand that you don't have the time to 
fix it quickly, but that's not the point: people are patient, but they 
obviously don't like to be… dismissed like this.
If you need help for maintaining systemd related packages, please ask.
Adrien
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20250909/0914e328/attachment.htm>