Bug#809773: ifupdown: post 0.7.54 ifupdown breaks all kinds of services

2016-01-13 Thread Martin Pitt
Hello, Christoph Anton Mitterer [2016-01-07 21:08 +0100]: > Well except for depending on network.target, which AFAIU should mean > that all network interfaces are bought up. No, this is *not* what network.target is; this is primarily for correct shutdown order. What you mean is

Bug#809773: ifupdown: post 0.7.54 ifupdown breaks all kinds of services

2016-01-13 Thread Guus Sliepen
On Wed, Jan 13, 2016 at 04:20:22PM +0100, Martin Pitt wrote: > Before=network.target shutdown.target network-online.service > > but this is a typo -- this should be "network-online.target", not > ".service". Then at least the "auto" interfaces would work as > intended. Guus, can you please fix

Bug#809773: ifupdown: post 0.7.54 ifupdown breaks all kinds of services

2016-01-07 Thread Guus Sliepen
severity 809773 important thanks On Sun, Jan 03, 2016 at 10:53:24PM +0100, Christoph Anton Mitterer wrote: > Severity: critical > Justification: breaks unrelated software [...] > I've just upgraded from 0.7.54 to 0.8.5 and after rebooting the server, > all kinds of daemons didn't come up anmore,

Bug#809773: ifupdown: post 0.7.54 ifupdown breaks all kinds of services

2016-01-07 Thread Guus Sliepen
On Thu, Jan 07, 2016 at 08:11:48PM +0100, Christoph Anton Mitterer wrote: > > First, this is not a critical bug. No unrelated software is actually > > broken, it's just that at boot, apparently some services are started > > earlier than your network devices are configured. > Quoting: > >critical

Bug#809773: ifupdown: post 0.7.54 ifupdown breaks all kinds of services

2016-01-03 Thread Christoph Anton Mitterer
Package: ifupdown Version: 0.8.5 Severity: critical Justification: breaks unrelated software Hi Guus. I've just upgraded from 0.7.54 to 0.8.5 and after rebooting the server, all kinds of daemons didn't come up anmore, e.g. BIND: # systemctl status bind9.service -ln 1 ● bind9.service - BIND