On Fri, 25 Apr 2025 22:28:37 +0100 Roy Marples <rsmarp...@gmail.com> wrote: > On Fri, 25 Apr 2025 22:24:18 +0200 Martin Hostettler <textsh...@uchuujin.de> > wrote: > > On Fri, 11 Apr 2025 10:18:16 +0200 Daniel =?utf-8?Q?Gr=C3=B6ber?= > > <d...@darkboxed.org> wrote: > > > Control: severity -1 serious > > > Justification: Breaks unrelated software > > > Control: owner -1 d...@darkboxed.org > > > Control: user debian-rele...@lists.debian.org > > > Control: usertag -1 + bsp-2025-04-at-vienna > > > > > > I'm raising the severity of this bug after reading up on rc_policy. > > > > > > > Is it really better do have openresolv permanently removed from trixie? > > > > Given the soft freeze rules and the automatic removal of packages with RC > > bugs keeping this at RC level will leave debian trixie without this package. > > > > Otherwise i think this should be downgraded, as it is should always be > > possible to install resolvconf instead. > > > > Or maybe a fix could be found? > > > > Regards, > > > > - Martin Hostettler > > > > > > In /etc/resolvconf.conf you can set either libc=NO or resolv_conf=/dev/null > openresolv supports the use case where / is RO like a cd and /etc/resolv.conf > is a symlink to /var/run/resolv.conf > > Roy
Which, once again, demonstrates the excessive severity this bug was given. "Doesn't fit Daniel's particular usage case" really isn't a justification for marking this bug as Serious. This is fully configurable. It's an important bug, at best. Martin-Éric
