[arch-general] netcl leaves network down until reenable performed - do we need note?

[David C. Rankin]

Archdevs,

  I have two computers using netctl, one for a static and one for a dhcp
address. After the last update on May, 3,

netctl (1.22-1 -> 1.23-1)

all remained fine and old profiles generated as subservices in
/etc/systemd/system, such as:

netctl\@rlf_network\\x2dstatic.service

continued to bring the network up. However within the past week there was a
change, likely to systemd 246, that no longer respects the subservices
originally created by netctl. Now attempting at reboot causes the network to
fail completely. Not good for remotely adminned boxes.

What is required is a "reenable" of the netctl profile. Doing so will remove
the old subservice and symlinks and replace then with a directory in
/etc/systemd/system of same name as the old subservice, but with a ".d"
appended that now contains a "profile.conf", e.g.

netctl at rlf_network\x2dstatic.service.d/
└── profile.conf

However, there is no note or warning during update that any manual
intervention will be needed. That will leave anyone adminning a remote arch
install with netctl with a box that is unreachable and has no network.

Shouldn't there be a warning about this change generated on update? Arch is
always pretty good about warning when manual interaction is required -- and
this is a biggie.

Couldn't there also be a post install that does a reenable for each netctl
profile found in /etc/systemd/system as another option to avoid this SNAFU?

-- 
David C. Rankin, J.D.,P.E.