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. On Mon, Dec 04, 2023 at 12:30:03PM +0100, Daniel Gröber wrote: > On Mon, Dec 04, 2023 at 11:41:57AM +0100, Daniel Gröber wrote: > > This is similar to how networkmanager and systemd-resolvd handle > > ownership conflicts and following this protocol will ensure only one > > (or none in my case :) managment system will try to change > > resolv.conf. > > Additional datapoint the old resolvconf package also follows this > protocol. It prints a warning and doesn't touch resolv.conf: > > # resolvconf -u > /etc/resolvconf/update.d/libc: Warning: /etc/resolv.conf is not a > symbolic link to /run/resolvconf/resolv.conf > > It does however have logic in it's postinst to overwrite /etc/resolv.conf > with it's symlink on installation. > > --Daniel
signature.asc
Description: PGP signature
