Bug#968015: resolvconf-pull-resolved.service fails with systemd 246-2

On Thu, Sep 3, 2020 at 3:02 PM Michael Biebl wrote: > > Hi Dan Hi Michael > > Am 03.09.20 um 20:42 schrieb Dan Streetman: > > On Mon, Aug 17, 2020 at 4:42 AM Michael Biebl wrote: > and over again. > >> > >> Afaics, the simplest solution, is to simply drop > >> > >>

Bug#968015: resolvconf-pull-resolved.service fails with systemd 246-2

Hi Dan Am 03.09.20 um 20:42 schrieb Dan Streetman: > On Mon, Aug 17, 2020 at 4:42 AM Michael Biebl wrote: and over again. >> >> Afaics, the simplest solution, is to simply drop >> >> PathExists=/run/systemd/resolve/stub-resolv.conf >> >> and instead add a >> >> [Install] >>

Bug#968015: resolvconf-pull-resolved.service fails with systemd 246-2

On Mon, Aug 17, 2020 at 4:42 AM Michael Biebl wrote: > > Control: severity -1 serious > Control: tags -1 + patch > > Hi everyone, > > I think the effects of this issue are severe enough, that it needs to be > fixed for bullseye. In other words, it should be RC > > On Sat, 08 Aug 2020 13:13:44

Bug#968015: resolvconf-pull-resolved.service fails with systemd 246-2

Am 17.08.20 um 10:41 schrieb Michael Biebl: > I've attached a prospective patch. > > Dan, Dimitri, would welcome your feedback here, since most of the > resolvconf/resolved integration is seemingly coming from you. Btw, I'll add a versioned Breaks: resolvconf (<< 1.83) to systemd, assuming the

Bug#968015: resolvconf-pull-resolved.service fails with systemd 246-2

Control: severity -1 serious Control: tags -1 + patch Hi everyone, I think the effects of this issue are severe enough, that it needs to be fixed for bullseye. In other words, it should be RC On Sat, 08 Aug 2020 13:13:44 +0200 =?utf-8?q?Thomas_M=C3=BChlbacher?= wrote: > I noticed that there

Bug#968015: resolvconf-pull-resolved.service fails with systemd 246-2

I noticed that there were already two related bugreports, with Michael Biebl providing a solution for the issue: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967906 And to a lesser degree this one, I suppose: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968009 I tried the container

Bug#968015: resolvconf-pull-resolved.service fails with systemd 246-2

I was also hit by this bug. The rate of logspam caused by the failure message was so intense that my laptop's SATA SSD was filling up at hundreds of MiB per minute. The I/O flood made everything slow down; login barely worked, bash-completion tabbing took 5-10 s, and figuring out which process(es)

Bug#968015: resolvconf-pull-resolved.service fails with systemd 246-2

Package: resolvconf Version: 1.82 Since `systemd` version 246-2, systems using `systemd-resolved` fail to reach the `default.target` if `resolvconf` is also installed. Steps to reproduce the error in a sysroot (`less` and `bash-completion` are just for comfort in debugging/reading logs):