Package: nut-client Version: 2.7.4-13 Severity: wishlist Dear Maintainer,
Trying to work out support for a new UPS I acquired, I found this upstream github issue about supporting the protocol needed to get full information out of my new hardware: https://github.com/networkupstools/nut/issues/139 (I am fastcat in that discussion). One item that came out of it: being able to install apcupsd side-by-side would help work around this issue, but is not currently possible due to conflicts between the packages. AFAICT, this conflict centers _solely_ on the sysvinit script for nut-client, or more precisely the /etc/init.d/ups-monitor symlink. This is no longer provided by upstream, but rather by the debian package. If this symlink was removed, the conflict on apcupsd could be dropped, and the two packages installed side-by-side. Since this is just a symlink, I think it may be safe to remove it. I think it should be simple enough to write some post-upgrade logic to rewrite any /etc/rcN.d links to the proper name, if they even exist? -- System Information: Debian Release: 11.1 APT prefers stable-updates APT policy: (990, 'stable-updates'), (990, 'stable-security'), (990, 'stable'), (500, 'testing'), (490, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-9-amd64 (SMP w/16 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages nut-client depends on: ii adduser 3.118 ii init-system-helpers 1.60 ii libc6 2.32-4 ii libupsclient4 2.7.4-13 ii lsb-base 11.1.0 Versions of packages nut-client recommends: ii bash-completion 1:2.11-2 Versions of packages nut-client suggests: pn nut-monitor <none> -- Configuration Files: /etc/nut/nut.conf changed [not included] /etc/nut/upsmon.conf [Errno 13] Permission denied: '/etc/nut/upsmon.conf' /etc/nut/upssched.conf [Errno 13] Permission denied: '/etc/nut/upssched.conf' -- no debconf information
