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 07:18:26 -0700	[thread overview]
Message-ID: <4ea2f745-1e75-ad88-57fa-d0d1547586be@gmail.com> (raw)
In-Reply-To: <1922379.ZbMImBqxyj@dell_xps>

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


  reply	other threads:[~2017-10-28 14:18 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 [this message]
2017-10-28 16:48   ` Mick
2017-10-28 23:51     ` Daniel Frey
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=4ea2f745-1e75-ad88-57fa-d0d1547586be@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