[Bug 1313712] Re: Trusty's libselinux1 is causes issues with Precise's upstart during dist-upgrade
    Dimitri John Ledkov 
    launchpad at surgut.co.uk
       
    Mon Apr 28 13:37:31 UTC 2014
    
    
  
upstart in precise does not link/use libselinux, nor supports stateful re-execution.
If one re-execs precise's upstart, it looses state of all jobs.
upstart in trusty does support stateful re-execution and links against libselinux.
I'll inspect libselinux post-install scripts, but it should only re-execute upstart if and only if "initctl version" is > 1.10
-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to libselinux in Ubuntu.
https://bugs.launchpad.net/bugs/1313712
Title:
  Trusty's libselinux1 is causes issues with Precise's upstart during
  dist-upgrade
Status in “libselinux” package in Ubuntu:
  Triaged
Status in “libselinux” source package in Trusty:
  Triaged
Status in “libselinux” source package in Utopic:
  Triaged
Bug description:
  Hi everyone,
  During troubleshooting of bug http://pad.lv/1303891 I've also
  discovered that Precise's upstart version doesn't work with Trusty's
  libselinux1. This is a major issue during a dist-upgrade from Precise
  to Trusty as upstart is severely affected by this and looses track of
  service PIDs which prevents service reloads.
  Can someone add a Breaks for Precise's upstart version to Trusty's
  libselinux1 debian/control file?
  Reproduction instructions:
  Install Ubuntu 12.04.4.
  $ sudo apt-get update -qq && sudo apt-get dist-upgrade -qqy
  <no output; no updates>
  $ initctl list
  avahi-daemon start/running, process 765
  ...
  $ sudo sed -i 's/precise/trusty/g' /etc/apt/sources.list
  $ sudo apt-get update -qq
  <no ouput; no errors>
  $ sudo apt-get install libselinux1 -y
  ...
  New dmesg lines:
  [ 256.032898] init: Re-executing /sbin/init
  New syslog lines:
  Apr 23 14:51:40 test upstart-socket-bridge[1090]: Disconnected from Upstart
  Apr 23 14:51:40 test upstart-udev-bridge[595]: Disconnected from Upstart
  $ initctl list
  avahi-daemon stop/waiting
  ...
  Upstart lost track of service PIDs. Commands like 'initctl reload
  dbus' will fail.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libselinux/+bug/1313712/+subscriptions
    
    
More information about the foundations-bugs
mailing list