A simple way to fix this would be to deploy a newer version of virtuoso- nepomuk for Trusty (or for Xenial, depending on the order of upgrades), with a fixed content in /etc/init.d/virtuoso-nepomuk (the only necessary change is to add the "### END INIT INFO" line).
Another approach would be to be more flexible when reading the /etc/init.d/* files, and assume the "### END INIT INFO" line at the end of the comment lines started by "### BEGIN INIT INFO", if this end line is not there. That would allow to handle this issue on other packages that might be in the same case. I would find that much cleaner, but it might be a bit more difficult. A completely different approach would be to check the /etc/init.d/* files before starting the upgrade, and prevent the user from starting the upgrade if a non-compliant file is found. Ideally, it would also tell him which package causes the issue, and suggest to remove it. In any case, leaving an end-user with a half-upgraded system like that is VERY bad. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1610241 Title: Failed upgrade from 14.04 to 16.04 : package sysv-rc 2.88dsf-59.3ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1610241/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
