On Fri, Jan 14, 2011 at 04:07:58PM -0800, Russ Allbery wrote: > Roger Leigh <firstname.lastname@example.org> writes: > > > I've yet to find a single system which upgraded to insserv cleanly. > > This is mostly due to removed packages which need fully purging to > > remove the last traces of old init scripts which break the process. > > Huh. Every system I've upgraded had no problems. What is the failure > mode? What happens on those systems? Like Mike said in his reply, sysv-rc fails to configure fully due to the presence of init scripts incompatible with insserv. It refuses to complete until they are gone. You can live with this, but it's not ideal. > > This has proven to be the case on every system I've migrated so far, and > > it is a real pain to identify each offending script and then find which > > package it belonged to and purge it. > > dpkg -S would generally tell you, no? We could document how to do that in > the release notes. 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. Because the error message only lists the first offending file, rather than listing them all, you then need to repeat this until you've weeded out all the files one by one until eventually it succeeds. 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. Regards, Roger -- .''`. Roger Leigh : :' : Debian GNU/Linux http://people.debian.org/~rleigh/ `. `' Printing on GNU/Linux? http://gutenprint.sourceforge.net/ `- GPG Public Key: 0x25BFB848 Please GPG sign your mail.
Description: Digital signature