[Jamin W. Collins] > Perhaps listing a conflict with package versions prior to those that > have the fixed init scripts would be enough. However, this would > need to be tested. I don't have details on hand for which specific > versions of packages had init scripts that caused the issue, I'm > sorry.
I suspect it would have to be solved on a case by case basis, as we are talking about packages with bogus or incomplete boot script ordering information. > Would it be possible to have innserv only warn and not break the > upgrade? By this I mean allow the rest of the upgrade to proceed. I > believe doing so would result in the fixed packages getting > installed and thereby also mitigating the issue. I doubt it, given that the incorrect boot ordering information exist in the package in question, and continuing might leave the system in a non-bootable state anyway. So the options seem to be to abort the upgrade and require manual intervention, or continue the upgrade and perhaps end up with a non-bootable system. The former seem like a better option to me, to avoid silent breakage. -- Happy hacking Petter Reinholdtsen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
