the bug still exists in stable (version 1.14.0-2) and from what i remember also in testing.
steps to reproduce: 1) insserv -r service 2) aptitude full-upgrade result: service is running again if the service was in the upgrade may i propose this be more than wishlist: for one, the expected behavior is that package upgrades do not override user- made system configurations without asking (this is the case at least when dealing with config files from what i've seen). disabling a service with insserv is, from a user view, just as much part of a system configuration as editing some .conf file, hence should be respected just as much. second, the practical implication is a minor security risk imo: after reading some article about a samba vulnerability, i did 'pgrep smb' on my playground 'server' and was very surprised to find samba running, because i remembered having disabled it and did not think i would have to re-disable it at any time. i guess the problem is that aptitude automatically makes insserv enable the service, regardless of previous state. regards, andreas
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Pkg-sysvinit-devel mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-sysvinit-devel
