[Touch-packages] [Bug 1585589] Re: drop upstart-sysv

2016-06-22 Thread Launchpad Bug Tracker
This bug was fixed in the package upstart - 1.13.2-0ubuntu26 --- upstart (1.13.2-0ubuntu26) yakkety; urgency=medium * Disable upstart-sysv package. (LP: #1585589) -- Martin Pitt Wed, 22 Jun 2016 15:51:51 +0200 ** Changed in: upstart (Ubuntu) Status: Fix Committed => Fix

[Touch-packages] [Bug 1585589] Re: drop upstart-sysv

2016-06-22 Thread Martin Pitt
** Changed in: upstart (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1585589 Title: drop upstart-sysv Status in upstart

[Touch-packages] [Bug 1585589] Re: drop upstart-sysv

2016-06-22 Thread Launchpad Bug Tracker
** Branch linked: lp:~ubuntu-core-dev/upstart/ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1585589 Title: drop upstart-sysv Status in upstart package in Ubuntu:

[Touch-packages] [Bug 1585589] Re: drop upstart-sysv

2016-05-25 Thread Adam Conrad
It's not so much about maintaining upstart as it is about maintaining upstart support in every daemon, and making sure the boot sequence continues to function well, etc. That's completely wasted effort, and the only reason we made sure it continued functioning up until Xenial was to make sure that

[Touch-packages] [Bug 1585589] Re: drop upstart-sysv

2016-05-25 Thread Sworddragon
In that case would it not be possibly better to move Upstart from main to universe and keep the optional upstart-sysv dependency in init? This way users can continue to use (and theoretically develop) Upstart while the maintainers of main don't need to maintain Upstart anymore. -- You received th

[Touch-packages] [Bug 1585589] Re: drop upstart-sysv

2016-05-25 Thread Martin Pitt
We currently keep "upstart" for the session init, but we are working on replacing those: https://blueprints.launchpad.net/ubuntu/+spec/convergence-y-replace- upstart As we don't want to support two init systems, there is no upstart maintainer any more, and nobody tests upstart for system boot, we'

[Touch-packages] [Bug 1585589] Re: drop upstart-sysv

2016-05-25 Thread Sworddragon
So Upstart gets completely removed or is it really just the init-part (upstart-sysv) that gets removed so that Upstart continues to work in 16.10+ besides systemd to run legacy jobs? Otherwise I have to migrate a few custom jobs to systemd before Ubuntu 16.10 gets released in october. -- You rece

[Touch-packages] [Bug 1585589] Re: drop upstart-sysv

2016-05-25 Thread Martin Pitt
>From 16.10 on, upstart-sysv is not supported any more and hence it was dropped as an "init" alternative. I just wanted to leave some time between the steps to eliminate it, to check some potential fallout. E. g. Ubuntu Touch still has that seeded, and we need to sort this out first. ** Summary ch