← Back to team overview

touch-packages team mailing list archive

[Bug 1436956] Re: Critical system files such as /sbin/shutdown and /sbin/init missing after updating upstart

 

I think we intended to make "init" Essential again after the systemd
switch, and this somehow slipped our minds, or we hadn't noticed any
dire consequences of not doing so.  I've done this now, and will monitor
if fixing this bug will cause others elsewhere.

** This bug is no longer a duplicate of bug 1436691
   init package is missing

** Changed in: upstart (Ubuntu)
       Status: Incomplete => In Progress

** Changed in: upstart (Ubuntu)
     Assignee: (unassigned) => Adam Conrad (adconrad)

-- 
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/1436956

Title:
  Critical system files such as /sbin/shutdown and /sbin/init missing
  after updating upstart

Status in upstart package in Ubuntu:
  In Progress

Bug description:
  1)
  Description:    Ubuntu Vivid Vervet (development branch)
  Release:        15.04

  2)
  upstart:
    Installed: 1.13.2-0ubuntu9
    Candidate: 1.13.2-0ubuntu10
    Version table:
       1.13.2-0ubuntu10 0
          500 http://mirror.cloud.online.net/ubuntu-ports/ vivid/main armhf Packages
   *** 1.13.2-0ubuntu9 0
          100 /var/lib/dpkg/status

  3) What you expected to happen
  System continues to run normally with critical system files (listed below) intact.

  4) What happened instead
  The following critical system files are all missing after updating the upstart package using apt-get:
  /sbin/halt
  /sbin/init
  /sbin/poweroff
  /sbin/reboot
  /sbin/runlevel
  /sbin/shutdown
  /sbin/telinit

  This is a serious bug which could prevent rebooting/shutdown of the OS
  and completely disable it due to missing /sbin/init.

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


References