Package: insserv Version: 1.12.0-10 Severity: grave Justification: causes non-serious data loss
If a sysadmin changes the priority of one of the init scripts manually, insserv must not ignore this change and simply delete the link, but it does. To reproduce simply change the priority of one script manually before enabling insserv. This definitely loses data (namely the priority the process was supposed to run in) and might even make the system unbootable. Michael -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (101, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.30-1-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages insserv depends on: ii debconf [debconf-2.0] 1.5.27 Debian configuration management sy ii initscripts 2.87dsf-2 scripts for initializing and shutt ii libc6 2.9-24 GNU C Library: Shared libraries ii sysv-rc 2.87dsf-2 System-V-like runlevel change mech ii sysvinit-utils 2.87dsf-2 System-V-like utilities insserv recommends no packages. Versions of packages insserv suggests: pn bootchart <none> (no description available) -- debconf information: * insserv/enable: false -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
