> Policy does not dictate what happens, but describes current practice > AFAICT. So with changing practice, it's quite normal that policy still > tells something different AFAICS.
It's not about policy needing an update, but about the package deleting user changes that were doen the right way according to policy. After insser has been activated the admin has to make the changes by changing the dependency headers, right. But if he made changes before installing insserv must not override them without notice. > I guess a debconf message explaining that the dependencies have to be > changed to change the boot order would be in order. I don't think this suffices. Every maintainance script that moves some startup links to a different level was supposed to check first whether those links are still in the default level and not touch them if they weren't. Why can't we expect the same from insserv? Michael -- Michael Meskes Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org ICQ: 179140304, AIM/Yahoo/Skype: michaelmeskes, Jabber: mes...@jabber.org Go VfL Borussia! Go SF 49ers! Use Debian GNU/Linux! Use PostgreSQL! -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
