public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: lee <lee@yagibdah.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: blockage
Date: Sun, 22 Mar 2015 19:08:12 +0100	[thread overview]
Message-ID: <87k2y8zz03.fsf@heimdali.yagibdah.de> (raw)
In-Reply-To: <550ED96E.1090300@gentoo.org> (Jonathan Callen's message of "Sun, 22 Mar 2015 11:02:06 -0400")

Jonathan Callen <jcallen@gentoo.org> writes:

> On 2015-03-22 09:04, lee wrote:
>> Tom H <tomh0665@gmail.com> writes:
>> 
>>> On Sun, Mar 22, 2015 at 7:31 AM, Alan McKinnon
>>> <alan.mckinnon@gmail.com> wrote:
>>>> 
>>>> It looks to me like sysvinit-2.88-r7 was stabilized and the
>>>> maintainer of apcupsd didn't notice. From the ebuild for
>>>> apcupsd-3.14.8-r2:
>>>> 
>>>> DEPEND=" ||      ( >=sys-apps/util-linux-2.23[tty-helpers] 
>>>> <=sys-apps/sysvinit-2.88-r4 sys-freebsd/freebsd-ubin )
>>>> 
>>>> What I suggest is copy that ebuild to your local overlay and
>>>> update the DEPEND to <=sys-apps/sysvinit-2.88-r7 and redigest
>>>> 
>>>> If that gives a correct update path for world, then file a bug
>>>> against apcupsd.
>>> 
>>> Some commands were moved from sysvinit to util-linux, and these 
>>> commands are required by apcupsd and are included in util-linux
>>> if it's compiled with the "tty-helpers" use flag.
>> 
>> Is this somehow reflected in the dependencies?  And how could I
>> deal with the multiple versions of util-linux that seem to be
>> required?
>> 
>> Perhaps I should forcefully update util-linux and use tty-helpers
>> so that apcupsd still works in case I reboot.  But what other
>> problems might that cause?
>> 
>> 
>> What am I supposed to think?  Should we not update unless no
>> problems are listed and just wait in case there are some,
>> potentially having to wait indefinitely?  How about security
>> updates then?
>> 
>> 
>
> It is reflected in the dependencies by the fact that the first dep
> (and generally the one chosen by portage) requires a new-enough
> version of util-linux *with the "tty-helpers" USE flag enabled*.  You
> don't need multiple versions of anything installed.  If you just add
> "sys-apps/util-linux tty-helpers" to your /etc/portage/package.use
> file and try again, you will likely find that portage will update
> everything for you without any further issues.

Oh that actually works!  How is one supposed to know that this use flag
must be added?


-- 
Again we must be afraid of speaking of daemons for fear that daemons
might swallow us.  Finally, this fear has become reasonable.


  reply	other threads:[~2015-03-22 18:13 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-22  3:24 [gentoo-user] blockage lee
2015-03-22  5:21 ` [gentoo-user] blockage Jonathan Callen
2015-03-22 11:00   ` lee
2015-03-22  9:24 ` [gentoo-user] blockage Alan McKinnon
2015-03-22 10:45   ` lee
2015-03-22 11:31     ` Alan McKinnon
2015-03-22 12:09       ` Tom H
2015-03-22 13:04         ` lee
2015-03-22 15:02           ` [gentoo-user] blockage Jonathan Callen
2015-03-22 18:08             ` lee [this message]
2015-03-22 21:22               ` Alan McKinnon
2015-03-22 21:54                 ` Dale
2015-03-23  9:55                 ` Peter Humphrey
2015-03-23  9:59                   ` Alan McKinnon
2015-03-23 10:04                     ` Peter Humphrey
2015-03-23 22:07                     ` James
2015-03-28 13:44                       ` lee

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=87k2y8zz03.fsf@heimdali.yagibdah.de \
    --to=lee@yagibdah.de \
    --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