This bug was fixed in the package nut - 2.7.4-9ubuntu1
---
nut (2.7.4-9ubuntu1) eoan; urgency=medium
* Merge with Debian unstable (LP: #1505288). Remaining changes:
- remove Build-Depends on libpowerman0-dev
- remove nut-powerman-pdu
+ debian/control: remove nut-powerm
https://launchpad.net/ubuntu/+source/nut/2.7.4-9ubuntu1 will close this
bug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1505288
Title:
package nut-client 2.7.1-1ubuntu5 failed to install/upgrade:
Thanks for the explanation Laurent!
Now things make sense to us as well I guess.
And together with the fact that install/remove no more is an issue in
the new versions things are good then.
** Merge proposal linked:
https://code.launchpad.net/~paelzer/ubuntu/+source/nut/+git/nut/+merge/370947
"nut-monitor" is a GTK+ application to see the state of the UPS's
nut-monitor.service is the systemd service file starting the client part
of nut, upsmon (aka ups monitor). nut-client was the name of the LSB
initscript that was doing the same thing. the nut-client.service symlink
is present to let
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 r
Hi Barry,
the stale missed removal of the conffile seems still around but I fail to see
the installation issue.
When upgrading from trusty to xenial I see:
/etc/systemd/system/nut-client.service ->
/lib/systemd/system/nut-monitor.service
But even a follow on remove, install, reinstall, purge -
Your issue was around:
Setting up nut-client (2.7.1-1ubuntu5) ...
Failed to restart nut-client.service: Unit nut-client.service failed to load:
No such file or directory.
invoke-rc.d: initscript nut-client, action "restart" failed.
That is the name of the now inexistent link.
But systemd uses t
More headscratchers:
% locate nut-client.service | xargs ls -l
lrwxrwxrwx 1 root root 39 Jan 10 2014 /etc/systemd/system/nut-client.service
-> /lib/systemd/system/nut-monitor.service
-rw-r--r-- 1 root root 0 Jan 10 2014
/var/lib/systemd/deb-systemd-helper-enabled/nut-client.service
% ls -l /e
Removing the bogus symlink lets me at least remove nut, nut-client, and
nut-server and reinstall those packages.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1505288
Title:
package nut-client 2.7.1
% sudo apt-get install --reinstall nut-client
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
3 not fully installed or removed.
After this operation, 0 B of additional disk
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1505288
Title:
package nut-client 2.7.1-1ubuntu5 failed to install/upgrade:
subprocess installed post-installati
11 matches
Mail list logo
