Hi Alex
Am 11.11.2017 um 00:33 schrieb Alex King:
> looks like everything that should be in /lib/systemd and
> /usr/lib/systemd is duplicated in both places?! I guess that is most
> likely a sysadmin typo, although the system was reloaded relatively
> recently and I have no idea how this could ha
On 12/11/17 00:53, Michael Biebl wrote:
Hi Alex
Am 11.11.2017 um 00:33 schrieb Alex King:
looks like everything that should be in /lib/systemd and
/usr/lib/systemd is duplicated in both places?! I guess that is most
likely a sysadmin typo, although the system was reloaded relatively
recently
Processing control commands:
> tags -1 = patch
Bug #881310 [systemd-container] systemd-container: systemd-nspawn containers
get non-functioning /etc/resolv.conf
Added tag(s) patch; removed tag(s) upstream and moreinfo.
--
881310: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881310
Debian B
Control: tags -1 = patch
Am 12.11.2017 um 00:33 schrieb Alex King:
> So it seems like this will be a problem for stretch systems with
> usrmerge enabled, and are not using systemd-resolved
Indeed, these are the conditions under which you can trigger this issue.
Looking through the git history,
