- To: debian-devel@lists.debian.org
- Subject: BROKEN! DO NOT UPGRADE (was: Re: Updated Debian 13: 13.1 released)
- From: Bjørn Mork <bjorn@mork.no>
- Date: Sat, 06 Sep 2025 17:44:55 +0200
- Message-id: <[🔎] 87qzwjfuvc.fsf@miraculix.mork.no>
- In-reply-to: <7b06eeee081abd616f9dcd62459176604f0a6fde.camel@debian.org> (Jean-Pierre Giraud's message of "Sat, 06 Sep 2025 15:01:46 +0200")
- References: <7b06eeee081abd616f9dcd62459176604f0a6fde.camel@debian.org>
> | systemd [64] | New upstream stable release | I am very disappointed that Debian has made a stable point release with a critical system package being this broken. Even being KNOWN broken. This is not the Debian I have been used to. Some network configurations result in systemd-networkd segfaulting in 257.8-1~deb13u1. The implications should be obvious. Fixing a system without network is hard. If the broken system is remote then it might even be impossible. And discovering that this bug has been known for a week and still released today makes me sad Further details are found in https://bugs.debian.org/1112535 Bjørn
Reply to:
- Follow-Ups:
- Re: BROKEN! DO NOT UPGRADE
- From: Bjørn Mork <bjorn@mork.no>
- Re: BROKEN! DO NOT UPGRADE
- Prev by Date: Re: Bug#1114180: libplacebo: FTBFS: dh_auto_build: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 ninja -j2 -v returned exit code 1
- Next by Date: Re: Bug#1113864: Replace -fcf-protection=full with -fcf-protection=return
- Previous by thread: Re: Closing bugs in experimental (was #1114180)
- Next by thread: Re: BROKEN! DO NOT UPGRADE (was: Re: Updated Debian 13: 13.1 released)
- Index(es):