public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Daniel Frey <djqfrey@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Alternatives to knutclient
Date: Sat, 28 Oct 2017 16:51:51 -0700	[thread overview]
Message-ID: <20a51a10-2c3b-bbcf-ab4e-98f8d2676fe5@gmail.com> (raw)
In-Reply-To: <2946670.lPvgj9kbiW@dell_xps>

On 10/28/2017 09:48 AM, Mick wrote:
> On Saturday, 28 October 2017 15:18:26 BST Daniel Frey wrote:
>> On 10/28/2017 01:58 AM, Mick wrote:
>>> Hi All,
>>>
>>> I've been using the net-misc/knutclient GUI application to provide
>>> information to desktop users of the state of the UPS.  Portage is telling
>>> me this package depends on Qt4, it has received no development upstream
>>> and is due to be ditched:
>>>
>>> !!! The following installed packages are masked:
>>> - net-misc/knutclient-1.0.5::gentoo (masked by: package.mask)
>>> /usr/portage/profiles/package.mask:
>>> # Andreas Sturmlechner <asturm@gentoo.org> (21 Oct 2017)
>>> # Dead upstream, depends on dead kdelibs4/Qt4.
>>> # Masked for removal in 30 days. Bug #629018
>>>
>>> Is there some other GUI front end for nut in portage I could use in its
>>> place?
>> Have you tried the one that comes with the nut package? There should be
>> one installed with it. Although, I can't remember if it docks in the tray.
>>
>> Dan
> 
> Thanks Dan,
> 
>  From what I see here there are number of GUI interfaces and NUT-Monitor
> seems to be the application built in nut:
> 
> http://networkupstools.org/projects.html#_graphical_desktop_clients
> 
> However, I'm not sure it was built in my case:
> 
> $ find /usr/bin -iname *nut*
> /usr/bin/binutils-config
> /usr/bin/nut-scanner
> /usr/bin/knutclient
> 
> This is how I built nut:
> 
>       Installed versions:  2.7.3(12:42:59 18/04/17)(ssl tcpd ups_drivers_al175
> ups_drivers_apcsmart ups_drivers_apcsmart-old ups_drivers_apcupsd-ups
> ups_drivers_bcmxcp ups_drivers_bcmxcp_usb ups_drivers_belkin
> ups_drivers_belkinunv ups_drivers_bestfcom ups_drivers_bestfortress
> ups_drivers_bestuferrups ups_drivers_bestups ups_drivers_blazer_ser
> ups_drivers_blazer_usb ups_drivers_clone ups_drivers_clone-outlet
> ups_drivers_dummy-ups ups_drivers_etapro ups_drivers_everups
> ups_drivers_gamatronic ups_drivers_genericups ups_drivers_isbmex
> ups_drivers_ivtscd ups_drivers_liebert ups_drivers_liebert-esp2
> ups_drivers_masterguard ups_drivers_metasys ups_drivers_mge-shut
> ups_drivers_mge-utalk ups_drivers_microdowell ups_drivers_nutdrv_qx
> ups_drivers_oldmge-shut ups_drivers_oneac ups_drivers_optiups
> ups_drivers_powercom ups_drivers_powerpanel ups_drivers_rhino
> ups_drivers_richcomm_usb ups_drivers_riello_ser ups_drivers_riello_usb
> ups_drivers_safenet ups_drivers_solis ups_drivers_tripplite
> ups_drivers_tripplite_usb ups_drivers_tripplitesu ups_drivers_upscode2
> ups_drivers_usbhid-ups ups_drivers_victronups usb xml -cgi -ipmi -selinux -
> snmp -ups_drivers_netxml-ups -ups_drivers_nut-ipmipsu -ups_drivers_snmp-ups -
> zeroconf)
> 
> What am I missing?
> 

Well, that's odd. I just built it and see nothing of the sort. I built 
it with all USE flags.

I am not using nut now, but I was trying it about a year ago. I did have 
a client (it wasn't knutclient), maybe it was removed from the tree. 
That's disappointing.

How much information do your users need? I'm running KDE5 with apcupsd 
and an APC UPS, and the battery monitor built in to KDE shows me that 
the battery is at 100% (it doesn't really say much else, though.)

Dan


  reply	other threads:[~2017-10-28 23:52 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-28  8:58 [gentoo-user] Alternatives to knutclient Mick
2017-10-28 14:18 ` Daniel Frey
2017-10-28 16:48   ` Mick
2017-10-28 23:51     ` Daniel Frey [this message]
2017-10-29  1:56       ` Dale
2017-10-29  8:49         ` Mick
2017-10-29 11:21           ` Dale
2017-10-29 19:01             ` Wols Lists
2017-10-29 19:11               ` Mick
2017-10-29 19:30                 ` Wols Lists
2017-10-29 21:38                 ` Neil Bothwick
2017-10-29 19:46               ` Dale
2017-10-30  9:10                 ` Peter Humphrey
2017-10-30 10:15                   ` Mick
2017-10-30 14:09                     ` Daniel Frey
2017-10-30 14:47                       ` Mick
2017-10-30 19:33                         ` Daniel Frey
2017-10-30 19:37                           ` Daniel Frey
2017-10-30 19:40                           ` Rich Freeman
2017-10-30 21:01                             ` Dale
2017-10-30 23:39                               ` Mick
2017-10-31  0:09                                 ` mad.scientist.at.large
2017-10-31 17:33                                   ` Wols Lists
2017-10-31 23:29                                     ` Peter Humphrey
2017-11-01 12:45                                       ` Wols Lists
2017-11-01 13:47                                         ` Peter Humphrey
2017-10-31  0:26                                 ` Dale
2017-10-31  0:55                             ` Daniel Frey
2017-10-30 20:51                         ` mad.scientist.at.large
2017-10-30 20:50                   ` Dale
2017-10-30 21:04                     ` Rich Freeman
2017-10-30 23:28                       ` Mick
2017-10-30 23:42                         ` Rich Freeman
2017-10-31 17:05                           ` Wols Lists
2017-10-31 17:13                             ` Rich Freeman
2017-10-31 16:56                         ` Wols Lists
2017-10-31 17:08                           ` Rich Freeman
2017-10-30 22:59                     ` Mick
2017-10-30 23:32                       ` Rich Freeman
2017-10-31 17:17                         ` Wols Lists

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20a51a10-2c3b-bbcf-ab4e-98f8d2676fe5@gmail.com \
    --to=djqfrey@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox