Bug#784083: cloud-init-local service should start before networking service

2015-11-23 Thread Charles Plessy
Control: clone -1 -2 Control: retitle -2 Broken LSB headers (cloud-init-local service should start before networking service) Control: retitle -1 Missing systemd targets (cloud-init-local service should start before networking service) Le Thu, Sep 24, 2015 at 07:18:07AM +0900, Charles Plessy a

Bug#784083: cloud-init-local service should start before networking service

2015-09-23 Thread Charles Plessy
Le Mon, Sep 07, 2015 at 06:04:06PM +0200, Michael Biebl a écrit : > > The bug reporter claims that cloud-init-local needs to run during early > boot (rcS) before networking (typically /etc/init.d/networking) has started. > If this is true, and cloud-init-local really needs to start that early, >

Bug#784083: cloud-init-local service should start before networking service

2015-09-07 Thread Michael Biebl
Control: found -1 0.7.6~bzr976-3 I looked at the cloud-init package in testing/unstable. The LSB header of /etc/init.d/cloud-init-local has ### BEGIN INIT INFO # Provides: cloud-init-local # Required-Start:$local_fs $remote_fs # Required-Stop: # Default-Start: 2 3 4 5 #

Bug#784083: cloud-init-local service should start before networking service

2015-05-02 Thread Mehdi Abaakouk
Package: cloud-init Version: 0.7.6~bzr976-2 Severity: normal Dear Maintainer, cloud-init doesn't provide systemd startup files but only the sysv one. So when systemd-sysv creates the compatibility startup files for systemd, cloud-init-local.service depends of 'sysinit.target', that depends of