On Wed, 03 Dec 2014 08:52:39 +0100 Matthias Urlichs
<matth...@urlichs.de> wrote:
> Package: nut-client
> Version: 2.7.2-1+b3
> Severity: serious
> Justification: 10.7.3
>
> An unconfigured package is expected to not fail installation.
>
> Setting up nut-client (2.7.2-1+b3) ...
> Job for nut-monitor.service failed. See "systemctl status
nut-monitor.service" and "journalctl -xe" for details.
> invoke-rc.d: initscript nut-client, action "start" failed.
> dpkg: error processing package nut-client (--configure):
> subprocess installed post-installation script returned error exit
status 1
> Errors were encountered while processing:
> nut-client
> Press Return to continue.
>
This is probably because you need to configure nut before it is able to
start successfully. The systemd services nut ships do not take into
account /etc/nut/nut.conf (which by default is set to none, which is
supposed to disable all the services). Not exactly sure how to go about
adding these types of checks to the systemd service... perhaps it would
be easier to just remove the systemd services and leave the init
scripts, at least for now.
--
Cameron Norman
