← Back to team overview

touch-packages team mailing list archive

[Bug 1351306] Re: Cannot uninstall upstart and install systemd-sysv

 

** Description changed:

  upstart is currently quite deeply wired into our dependencies. Even in a
  minimally bootstrapped chroot needs it, although this doesn't do any
  booting at all:
  
  # dpkg -P upstart
  dpkg: dependency problems prevent removal of upstart:
-  initscripts depends on upstart.
-  plymouth depends on upstart (>= 1.11-0ubuntu3).
+  initscripts depends on upstart.
+  plymouth depends on upstart (>= 1.11-0ubuntu3).
  
  On a desktop the list is quite a bit longer:
  
-  ubuntu-minimal depends on upstart.
-  avahi-daemon depends on upstart (>= 0.6.7-4).
-  friendly-recovery depends on upstart.
-  initscripts depends on upstart.
-  ureadahead depends on upstart (>= 0.6.0).
-  plymouth depends on upstart (>= 1.11-0ubuntu3).
-  dbus depends on upstart (>= 0.6.3-6).
-  unity-services depends on upstart.
-  init depends on upstart.
+  ubuntu-minimal depends on upstart.
+  avahi-daemon depends on upstart (>= 0.6.7-4).
+  friendly-recovery depends on upstart. (See bug 1351316, needs sysv/systemd script first)
+  initscripts depends on upstart.
+  ureadahead depends on upstart (>= 0.6.0).
+  plymouth depends on upstart (>= 1.11-0ubuntu3).
+  dbus depends on upstart (>= 0.6.3-6).
+  unity-services depends on upstart.
+  init depends on upstart.
  
  Most of the latter probably don't need to; versioned depends might be
  converted into equivalent versioned breaks, for others an alternative
  dependency might be considered. The main exception is that we are using
  session upstart on the desktop (unity-services etc.), for this we
  probably need to split out an upstart-sysv (for /sbin/init, reboot,
  halt, etc., similar to systemd-sysv) or an upstart-core (similar to
  sysvinit-core vs. sysvinit).

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

** Description changed:

  upstart is currently quite deeply wired into our dependencies. Even in a
  minimally bootstrapped chroot needs it, although this doesn't do any
  booting at all:
  
  # dpkg -P upstart
  dpkg: dependency problems prevent removal of upstart:
   initscripts depends on upstart.
   plymouth depends on upstart (>= 1.11-0ubuntu3).
  
  On a desktop the list is quite a bit longer:
  
   ubuntu-minimal depends on upstart.
   avahi-daemon depends on upstart (>= 0.6.7-4).
   friendly-recovery depends on upstart. (See bug 1351316, needs sysv/systemd script first)
   initscripts depends on upstart.
   ureadahead depends on upstart (>= 0.6.0).
   plymouth depends on upstart (>= 1.11-0ubuntu3).
   dbus depends on upstart (>= 0.6.3-6).
   unity-services depends on upstart.
-  init depends on upstart.
+  init depends on upstart. (Not important right now, switch to alternative deps once systemd is ready)
  
  Most of the latter probably don't need to; versioned depends might be
  converted into equivalent versioned breaks, for others an alternative
  dependency might be considered. The main exception is that we are using
  session upstart on the desktop (unity-services etc.), for this we
  probably need to split out an upstart-sysv (for /sbin/init, reboot,
  halt, etc., similar to systemd-sysv) or an upstart-core (similar to
  sysvinit-core vs. sysvinit).

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

Title:
  Cannot uninstall upstart and install systemd-sysv

Status in “avahi” package in Ubuntu:
  Fix Committed
Status in “dbus” package in Ubuntu:
  Fix Committed
Status in “plymouth” package in Ubuntu:
  Fix Committed
Status in “sysvinit” package in Ubuntu:
  Confirmed
Status in “upstart” package in Ubuntu:
  Triaged

Bug description:
  upstart is currently quite deeply wired into our dependencies. Even in
  a minimally bootstrapped chroot needs it, although this doesn't do any
  booting at all:

  # dpkg -P upstart
  dpkg: dependency problems prevent removal of upstart:
   initscripts depends on upstart.
   plymouth depends on upstart (>= 1.11-0ubuntu3).

  On a desktop the list is quite a bit longer:

   ubuntu-minimal depends on upstart.
   avahi-daemon depends on upstart (>= 0.6.7-4).
   friendly-recovery depends on upstart. (See bug 1351316, needs sysv/systemd script first)
   initscripts depends on upstart.
   ureadahead depends on upstart (>= 0.6.0).
   plymouth depends on upstart (>= 1.11-0ubuntu3).
   dbus depends on upstart (>= 0.6.3-6).
   unity-services depends on upstart.
   init depends on upstart. (Not important right now, switch to alternative deps once systemd is ready)

  Most of the latter probably don't need to; versioned depends might be
  converted into equivalent versioned breaks, for others an alternative
  dependency might be considered. The main exception is that we are
  using session upstart on the desktop (unity-services etc.), for this
  we probably need to split out an upstart-sysv (for /sbin/init, reboot,
  halt, etc., similar to systemd-sysv) or an upstart-core (similar to
  sysvinit-core vs. sysvinit).

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


References