drop upstart-sysv

[Removed by request]

I'm using Ubuntu 16.10 dev with init 1.33ubuntu2 and I'm noticing that it does now pre-depend on "systemd-sysv" instead of "systemd-sysv | upstart-sysv". Since init is essential and upstart-sysv conflicts with systemd-sysv this means it is not possible to install Upstart in a sane way anymore.

In case Upstart is not supported anymore maybe all related packages should be removed from the yakkety repository then (since Upstart can't be installed anymore with apt for the reasons above) to avoid confusion.

[Martin Pitt (pitti)]

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.

[Removed by request (removed3425744)]

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.

[Martin Pitt (pitti)]

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'll drop it at some point.

[Removed by request (removed3425744)]

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.

[Adam Conrad (adconrad)]

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 upgrades could run smoothly.

Putting alternate init systems in universe without also committing to support them would be naive at best, actively harmful to users, at worst.

[Launchpad Janitor (janitor)]

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 <email address hidden> Wed, 22 Jun 2016 15:51:51 +0200