[14:38] <Jef91> Is there a configure flag that allows upstart to build without tests?
[14:38] <Jef91> One of the tests is failing in my chroot and I want to just skip them
[14:47] <Jef91> this bug found my solution -> https://bugs.launchpad.net/upstart/+bug/888910
[14:58] <xnox> Jef91: if you are building an debian/ubuntu package, you can pass DEB_BUILD_OPTIONS=nocheck to skip executing the test-suite.
[14:59] <xnox> Jef91: that bug is fixed in later releases.
[14:59] <Jef91> xnox, that was the option I needed yes
[14:59] <Jef91> that bug I just linked has that noted in the comments
[14:59] <xnox> Jef91: a bug report with your full build-log would be helpful, for us to find out if there is an issue with environment, tests or upstart itself as exposed by a particular environment.
[15:06] <jodh> Jef91: can you also state on that bug which version of upstart you are attempting to build under sbuild?
[20:33] <detrout> Hi, I'm running debian unstable just figured out that cgroupfs-mount's initscript causes my system to hang while shuttingdown/rebooting.
[20:35] <detrout> My hunch is the upstart init script is missing a stop trigger
[20:36] <slangasek> it certainly does seem to be missing a stop condition
[20:36] <slangasek> which is inconsistent with the init script
[20:36] <slangasek> (i.e., the upstart job has no stop condition, the init script does)
[20:37] <slangasek> so yes, this would cause a hang on shutdown, because startpar sees that the init script should be ignored in favor of the upstart job, and stalls waiting for the upstart job to trigger, which never happens
[20:39] <slangasek> detrout: a one-line change to /etc/init/cgroupfs-mount.conf to 'stop on unmounted-remote-filesystems' should do the job
[20:39] <detrout> ok.
[20:39] <detrout> it'll take me a moment to be able to test that.
[20:39] <slangasek> I'm not sure if it should be 'stop on runlevel [016]' instead - it seems like that could fail if something currently has the mount points in use
[20:41] <detrout> I installed it so I could try docker.io
[22:21] <apes> What does having a symlink in /etc/init.d cause Upstart to do? Is it supported behavior?
[22:21] <apes> EG /etc/init.d/foo -> /etc/init.d/bar
[22:22] <apes> Also assuming both are listed in various runlevels
[22:22] <apes> EG /etc/rc.2/foo /etc/rc.2/bar