On 09/27/2013 12:38 AM, Petter Reinholdtsen wrote:
Do you have any idea how to solve it for everyone? Would it help if insserv list a conflict or break on the problematic package versions to make sure they are upgraded first? Which package version should be listed like that?
I don't have specific suggestions on how to fix it for everyone, but this has resulted in rather extreme breakage on each of the Debian systems that I've dist-upgraded. Which given my previous experience with Debian came as quite a shock. For less experienced users this would be an extremely poor user experience.
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.
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.
-- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
