>> For systemd portion, we carry the
>> systemd-networkd-resolvconf-update.service as a delta from Debian
> I'm not sure what you mean here; the systemd package in zesty is currently
> in sync with Debian.
Ok, it appears that post-16.04, systemd-networkd-resolvconf-update.service is dropped from the package in favor of debian/extra/units/systemd-resolved.service.d/resolvconf.conf, so this patch does not apply.
I have verified that there is no ordering bug post-16.04, provided that the changes to resolvconf are applied. /lib/systemd/system/systemd-resolved.service.d/resolvconf.conf causes systemd-resolved to notify resolvconf of its nameserver, if /run/resolvconf/enable-updates exists. /run/resolvconf/enable-updates exists if resolvconf.service is started. resolvconf.service is started Before=network-pre.target; network.target is After=network-pre.target; systemd-resolved.service is After=network.target. So only the change to resolvconf is needed for yakkety and beyond.
>> For systemd portion, we carry the networkd- resolvconf- update. service as a delta from Debian
>> systemd-
> I'm not sure what you mean here; the systemd package in zesty is currently
> in sync with Debian.
Ok, it appears that post-16.04, systemd- networkd- resolvconf- update. service is dropped from the package in favor of debian/ extra/units/ systemd- resolved. service. d/resolvconf. conf, so this patch does not apply.
I have verified that there is no ordering bug post-16.04, provided that the changes to resolvconf are applied. /lib/systemd/ system/ systemd- resolved. service. d/resolvconf. conf causes systemd-resolved to notify resolvconf of its nameserver, if /run/resolvconf /enable- updates exists. /run/resolvconf /enable- updates exists if resolvconf.service is started. resolvconf.service is started Before= network- pre.target; network.target is After=network- pre.target; systemd- resolved. service is After=network. target. So only the change to resolvconf is needed for yakkety and beyond.