>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 changed:

- init does leave no choice between upstart and systemd anymore
+ drop upstart-sysv

** Package changed: init-system-helpers (Ubuntu) => upstart (Ubuntu)

** Changed in: upstart (Ubuntu)
   Importance: Undecided => Medium

** Changed in: upstart (Ubuntu)
       Status: New => Triaged

** Changed in: upstart (Ubuntu)
     Assignee: (unassigned) => Martin Pitt (pitti)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to init-system-helpers in
Ubuntu.
https://bugs.launchpad.net/bugs/1585589

Title:
  drop upstart-sysv

Status in upstart package in Ubuntu:
  Triaged

Bug description:
  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1585589/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to