[Pkg-sysvinit-devel] Bug#850314: purge sysv-rc initscripts insserv startpar sysv-rc-conf leaves residue

[積丹尼 Dan Jacobson]

Package: initscripts
Version: 2.88dsf-59.8

Here it looks like the steps are simply not ordered correctly,

# aptitude purge sysv-rc initscripts insserv startpar sysv-rc-conf

Removing initscripts (2.88dsf-59.8) ...
Removing sysv-rc-conf (0.99-7) ...
Removing sysv-rc (2.88dsf-59.8) ...
Removing insserv (1.16.0-5) ...
Removing libcurses-ui-perl (0.9609-1) ...
Removing startpar (0.59-3.1) ...
Processing triggers for systemd (232-8) ...
Processing triggers for man-db (2.7.6.1-2) ...
(Reading database ... 153824 files and directories currently installed.)
Purging configuration files for startpar (0.59-3.1) ...
Purging configuration files for sysv-rc (2.88dsf-59.8) ...
dpkg: warning: while removing sysv-rc, directory '/var/lib/insserv' not empty so not removed
Purging configuration files for insserv (1.16.0-5) ...
Purging configuration files for initscripts (2.88dsf-59.8) ...
dpkg: warning: while removing initscripts, directory '/var/lib/urandom' not empty so not removed
Processing triggers for systemd (232-8) ...

One would think that if they were ordered correctly one wouldn't see
those messages.

But in fact no matter the order, there is still residue left behind:

# ls -Rl /var/lib/urandom
/var/lib/urandom:
total 1
-rw------- 1 root root 512 2014-07-12  random-seed

# ls -Rl /var/lib/insserv
/var/lib/insserv:
total 104
-rw-r--r-- 1 root root  3388 2009-08-05  bootscripts-20090805T0501-after.list
-rw-r--r-- 1 root root 63815 2009-08-05  bootscripts-20090805T0501.tar.gz
-rw-r--r-- 1 root root 35648 2009-08-05  run-20090805T0501.log