Comment 7 for bug 1505288

Continuing "more headscratchers":

/lib/systemd/system/nut-monitor.service belongs to nut-clients:

# dpkg -S /lib/systemd/system/nut-monitor.service
nut-client: /lib/systemd/system/nut-monitor.service

I'd think that should be in nut-monitor package right?
But then I realized:

lrwxrwxrwx 1 root root 19 Aug 5 10:32 /lib/systemd/system/nut-client.service -> nut-monitor.service
-rw-r--r-- 1 root root 253 Aug 5 10:32 /lib/systemd/system/nut-monitor.service

By default it enters (but not breaks) a disabled by default mode.
● nut-monitor.service - Network UPS Tools - power device monitor and shutdown controller
   Loaded: loaded (/lib/systemd/system/nut-monitor.service; enabled; vendor preset: enabled)
   Active: failed (Result: protocol) since Mon 2019-08-05 11:35:18 UTC; 36s ago
  Process: 23388 ExecStart=/sbin/upsmon (code=exited, status=0/SUCCESS)

Aug 05 11:35:18 e systemd[1]: Starting Network UPS Tools - power device monitor and shutdown controller...
Aug 05 11:35:18 e upsmon[23388]: upsmon disabled, please adjust the configuration to your needs
Aug 05 11:35:18 e upsmon[23388]: Then set MODE to a suitable value in /etc/nut/nut.conf to enable it
Aug 05 11:35:18 e systemd[1]: nut-monitor.service: Can't open PID file /run/nut/upsmon.pid (yet?) after start: No such file or directory
Aug 05 11:35:18 e systemd[1]: nut-monitor.service: Failed with result 'protocol'.
Aug 05 11:35:18 e systemd[1]: Failed to start Network UPS Tools - power device monitor and shutdown controller.

I'd think that should maybe be an alias and a proper package dependency.

But lets take that aside for a while.
Install/Re-Install/Upgrade seem to be fixed at this version.
Therefore I'll reference this bug at an upcoming merge.