Roger Leigh <rle...@codelibre.net> writes: > Yes, and this is what I did. It's just rather tedious to (IIRC) > repeatedly run "dpkg-reconfigure sysv-rc" and then find out which file > is offending, run "dpkg -S $file", and then purge it.
I've not looked at the mechanism involved at all, but it does seem like we should be able to print out all of the files that would cause failures. Maybe it's hard to continue from an error long enough to find additional files? That sounds like it's the thing that makes this the most tedious. If you got a list of all offending init scripts, we could document in the release notes that you need to run dpkg -S on each one to locate the relevant package and purge that package if you're no longer using it. > It would be better if an upgrade was possible without all this manual > work. It's been tedious for the handful of systems I've done this on so > far; I wouldn't like to need to do it for many more. It does make sense to not continue with enabling inserv if it can't be done safely, though, and I don't know how to distinguish programmatically between init scripts that can just be removed and ones the local admin needs to keep and fix. -- Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87ei8ft2de....@windlord.stanford.edu
