touch-packages team mailing list archive

[Launchpad Bug Tracker <1422681@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package upstart - 1.13.2-0ubuntu10

---------------
upstart (1.13.2-0ubuntu10) vivid; urgency=medium

  * Add upstart-sysv to mirror systemd-sysv behavior if upstart is chosen
    as the default init daemon: (LP: #1422681)
    - this fixes upstart not starting only with upstart-bin binary due to
      missing jobs.
    - upstart now contains upstart-bin binaries.
    - upstart-bin is a transitional package. Can be deleted in vivid+1.
    - removed some deprecated transition path for both debian and ubuntu.
    - ensure grub is updated when upstart-sysv is installed.
    - always get alternatives init and right default grub entries.
 -- Didier Roche <didrocks@xxxxxxxxxx>   Mon, 23 Mar 2015 09:51:12 +0100

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-touch-meta in
Ubuntu.
https://bugs.launchpad.net/bugs/1422681

Title:
  split out upstart-sysv

Status in init-system-helpers package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New
Status in ubuntu-touch-meta package in Ubuntu:
  New
Status in upstart package in Ubuntu:
  Fix Released

Bug description:
  After switching to systemd permanently (apt get install systemd-sysv) and purging the now not needed "upstart" package, I tried to boot with the upstart fallback option in grub, just to find out it doesn't work.
  It looks like important init files are still in the "upstart" package instead of "upstart-bin" and should probably be moved there to keep the upstart fallback option working.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1422681/+subscriptions