> I guess to preserve the status quo ante, we should indeed just remove
this new file systemd-resolve.conf.
I also think it's the good short-term solution, ie. to go back to how it
was before v250, until a better solution is found.
> e.g. by splitting of systemd-resolved into a separate packa
Am 17.03.22 um 11:59 schrieb Michael Biebl:
Mid to long term, I'd like us to find a better solution for this, e.g.
by splitting of systemd-resolved into a separate package.
Maybe this would also enable us to fix
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939904
I.e. once systemd-resol
On Thu, 10 Mar 2022 22:11:13 +0700 Arnaud Rebillout
wrote:
Package: systemd
Version: 250.3-2
Severity: normal
User: de...@kali.org
Usertags: origin-kali
Dear Maintainer,
Since v250, systemd moved the tmpfiles config for /etc/resolv.conf out
of the file tmpfiles.d/etc.conf and inside a new file
Am 10.03.22 um 16:11 schrieb Arnaud Rebillout:
Package: systemd
Version: 250.3-2
Severity: normal
User: de...@kali.org
Usertags: origin-kali
Dear Maintainer,
Since v250, systemd moved the tmpfiles config for /etc/resolv.conf out
of the file tmpfiles.d/etc.conf and inside a new file
tmpfiles.d/s
Package: systemd
Version: 250.3-2
Severity: normal
User: de...@kali.org
Usertags: origin-kali
Dear Maintainer,
Since v250, systemd moved the tmpfiles config for /etc/resolv.conf out
of the file tmpfiles.d/etc.conf and inside a new file
tmpfiles.d/systemd-resolve.conf. Cf:
https://github.com/syste
5 matches
Mail list logo
