Am Donnerstag, den 27.06.2019, 10:52 +0200 schrieb Paul Gevers:
> Hi Benjamin,
> On 25-06-2019 13:25, Benjamin Drung wrote:
> > The ionit.service fix for bug #919690 introduced a systemd
> > dependency
> > loop. systemd will break the loop at a (random?) place which can
> > make
> > boot behave incorrectly.
> Bah. One of the big reasons why you should fix your bugs earlier.
I discovered the failing ifup@.service in January while testing and
reported #919690 against ifupdown. On 2019-06-20 I troubleshooted this
issue further and discovered that it was a configuration issue caused
by ionit running too late. Then I reassigned it and fixed ionit.
> And to
> ask a nasty question, why didn't you spot this issue in the previous
I tested that version and checked that all systemd services were
running. Sadly the dependency loop was just mentioned in the dmesg
output. That's why I didn't saw it in my initial tests.
> > I fixed the dependency loop in ionit 0.3.2+really0.2.1-2. A debdiff
> > is
> > attached.
> > unblock ionit/0.3.2+really0.2.1-2
> Unblocked, thanks.
Debian & Ubuntu Developer
1&1 IONOS Cloud GmbH | Greifswalder Str. 207 | 10405 Berlin | Germany
E-mail: [hidden email] | Web: www.ionos.de
Head Office: Berlin, Germany
District Court Berlin Charlottenburg, Registration number: HRB 125506 B
Executive Management: Christoph Steffens, Matthias Steinberg, Achim