Bug#538959: package fails to remove: error: insserv must be disabled before it is removed, to...
Package: insserv Version: 1.12.0-10 Severity: important Fresh and clean sid chroot: # apt-get install file-rc Reading package lists... Done Building dependency tree... Done The following packages will be REMOVED: insserv sysv-rc The following NEW packages will be installed: file-rc WARNING: The following essential packages will be removed. This should NOT be done unless you know exactly what you are doing! sysv-rc (due to sysvinit) 0 upgraded, 1 newly installed, 2 to remove and 0 not upgraded. Need to get 36.6kB of archives. After this operation, 373kB disk space will be freed. You are about to do something potentially harmful. To continue type in the phrase 'Yes, do as I say!' ?] Yes, do as I say! [...] error: insserv must be disabled before it is removed, to error: make sure the boot system is still usable. error: To disable, run dpkg-reconfigure insserv dpkg: error processing insserv (--remove): subprocess installed pre-removal script returned error exit status 1 [...] This behaviour didn't exist before insserv 1.12.0-10. regards, -mika- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#538959: package fails to remove: error: insserv must be disabled before it is removed, to...
severity 538959 critical thanks Hi, 10:16 formorer Removing insserv ... 10:16 formorer error: insserv must be disabled before it is removed, to 10:16 formorer error: make sure the boot system is still usable. 10:16 formorer error: To disable, run dpkg-reconfigure insserv 10:16 formorer WHOLY FUCK 10:17 formorer info: Disabling dependency based boot system 10:17 formorer mv: cannot stat `/usr/sbin/update-rc.d.distrib': No such file or directory 10:17 formorer broken, totally broken 10:17 formorer I need to reinstall sysv-rc again to disable it -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#538959: package fails to remove: error: insserv must be disabled before it is removed, to...
[Alexander Wirt] severity 538959 critical thanks Hi, 10:16 formorer Removing insserv ... 10:16 formorer error: insserv must be disabled before it is removed, to 10:16 formorer error: make sure the boot system is still usable. 10:16 formorer error: To disable, run dpkg-reconfigure insserv 10:16 formorer WHOLY FUCK 10:17 formorer info: Disabling dependency based boot system 10:17 formorer mv: cannot stat `/usr/sbin/update-rc.d.distrib': No such file or directory 10:17 formorer broken, totally broken 10:17 formorer I need to reinstall sysv-rc again to disable it What was leading up to this? Why did you try to disable insserv? Insserv will become essential together with sysv-rc, and is not supposed to be simple to remove any more. Dependency based boot sequencing is going to become the default and suppoted boot sequencing method. I'll remove the option to disable it. Happy hacking, -- Petter Reinholdtsen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#538959: package fails to remove: error: insserv must be disabled before it is removed, to...
Petter Reinholdtsen schrieb am Tuesday, den 28. July 2009: [Alexander Wirt] severity 538959 critical thanks Hi, 10:16 formorer Removing insserv ... 10:16 formorer error: insserv must be disabled before it is removed, to 10:16 formorer error: make sure the boot system is still usable. 10:16 formorer error: To disable, run dpkg-reconfigure insserv 10:16 formorer WHOLY FUCK 10:17 formorer info: Disabling dependency based boot system 10:17 formorer mv: cannot stat `/usr/sbin/update-rc.d.distrib': No such file or directory 10:17 formorer broken, totally broken 10:17 formorer I need to reinstall sysv-rc again to disable it What was leading up to this? Why did you try to disable insserv? apt-get install file-rc Insserv will become essential together with sysv-rc, and is not supposed to be simple to remove any more. Dependency based boot sequencing is going to become the default and suppoted boot sequencing method. I'll remove the option to disable it. There are other implementations bootmechanisms like file-rc, upstart and so on. Don't break them! Really, really not amused about that insserv stuff. Alex -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#538959: package fails to remove: error: insserv must be disabled before it is removed, to...
[Alexander Wirt] What was leading up to this? Why did you try to disable insserv? apt-get install file-rc Right. Good to hear that it is the same problem as the initial report. May I ask why you are using file-rc? What advantages does it have over the current sysv-rc script with concurrent booting? There are other implementations bootmechanisms like file-rc, upstart and so on. Don't break them! This problem only affect file-rc. Upstart is using the sysv-rc scripts to call the init.d scripts, and insserv work fine with it. I see two good ways to move forward with this. One is to convert file-rc to use dependency based boot sequencing (for example by rewriting it and insserv to work well together), or drop file-rc from Debian. I would really love to work with the file-rc developers to get it to order the boot sequence using dependency information. Happy hacking, -- Petter Reinholdtsen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#538959: package fails to remove: error: insserv must be disabled before it is removed, to...
Petter Reinholdtsen schrieb am Tuesday, den 28. July 2009: [Alexander Wirt] What was leading up to this? Why did you try to disable insserv? apt-get install file-rc Right. Good to hear that it is the same problem as the initial report. May I ask why you are using file-rc? What advantages does it have over the current sysv-rc script with concurrent booting? It doesn't use insserv. And it is much simpler to administrate for small systems like laptops or desktops. There are other implementations bootmechanisms like file-rc, upstart and so on. Don't break them! This problem only affect file-rc. Upstart is using the sysv-rc scripts to call the init.d scripts, and insserv work fine with it. ehm. file-rc uses also the /etc/init.d/ scripts so this answer is not correct and there are other replacements I didn't mentioned. I see two good ways to move forward with this. One is to convert file-rc to use dependency based boot sequencing (for example by rewriting it and insserv to work well together), or drop file-rc from Debian. God no. Insserv is pure crap. Just fix your package its broken like hell. Is there any _good_ reason why it has to _depend_ on insserv? (insserv is fully optional, so there is no need for another essential package). I would really love to work with the file-rc developers to get it to order the boot sequence using dependency information. No, please accept that people don't like this. Alex -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#538959: package fails to remove: error: insserv must be disabled before it is removed, to...
* Petter Reinholdtsen p...@hungry.com [2009-07-28 13:38:04 CEST]: [Alexander Wirt] Removing insserv ... error: insserv must be disabled before it is removed, to error: make sure the boot system is still usable. error: To disable, run dpkg-reconfigure insserv info: Disabling dependency based boot system mv: cannot stat `/usr/sbin/update-rc.d.distrib': No such file or directory What was leading up to this? Why did you try to disable insserv? It doesn't matter why one would want to disable some package. The package has to be deinstallable fine, no matter how (semi) essential those packages are. If the package isn't able to get removed properly (without jumping though hoops) it's broken, it's as simple as that. Insserv will become essential together with sysv-rc, and is not supposed to be simple to remove any more. Please leave that part to the hooks in the package managers that already have the hoops of requesting users to do something specific to get it removed anyway - there is no need to add another layer here. So long, Rhonda -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#538959: package fails to remove: error: insserv must be disabled before it is removed, to...
* Petter Reinholdtsen p...@hungry.com [20090728 13:56]: [Alexander Wirt] What was leading up to this? Why did you try to disable insserv? apt-get install file-rc Right. Good to hear that it is the same problem as the initial report. May I ask why you are using file-rc? What advantages does it have over the current sysv-rc script with concurrent booting? Speaking for myself why I prefer file-rc: No symlink hell, copying/distributing just one single file which defines the boot setup is enough, option to 'grep $service /etc/runlevel.conf', it's deterministic and just works,... BTW: How do I know in which order my insserv based system will boot up? There are other implementations bootmechanisms like file-rc, upstart and so on. Don't break them! This problem only affect file-rc. Upstart is using the sysv-rc scripts to call the init.d scripts, and insserv work fine with it. Of course upstart isn't affected because it doesn't conflict with sysv-rc (which introduced the breakage). Why should it be such a big deal to fix the package so removing it works again? I see two good ways to move forward with this. One is to convert file-rc to use dependency based boot sequencing (for example by rewriting it and insserv to work well together), OK - but *please* make dependency based booting an option. or drop file-rc from Debian. Please NO. regards, -mika- signature.asc Description: Digital signature
