On 10/19/2013 02:08 PM, Petter Reinholdtsen wrote:
[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.
It may be bogus or incomplete boot script ordering information, but it
previously worked, keep that in mind. One does not expect a Debian
dist-upgrade from one stable release to another to result in a
non-functional system.
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.
The former effectively left me locked out of my systems. I had to
reboot every one of them to a single user root session to fix them as my
user existed only in LDAP and then unrelated init scripts caused the
upgrade to abort in such a way that my user could no longer be validated
for sudo. Had the upgrade proceeded, the system would have been in
complete working order (AFAICT).
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
