From: Allan Gottlieb <gottlieb@nyu.edu>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Update world message
Date: Mon, 17 Jul 2006 17:29:29 -0400 [thread overview]
Message-ID: <yu9hd1f2a4m.fsf@nyu.edu> (raw)
In-Reply-To: <200607172202.22968.michaelkintzios@gmail.com> (Mick's message of "Mon, 17 Jul 2006 22:02:06 +0100")
At Mon, 17 Jul 2006 22:02:06 +0100 Mick <michaelkintzios@gmail.com> wrote:
> On Monday 17 July 2006 11:19, Mick wrote:
>> On Monday 17 July 2006 10:27, Arnau Bria wrote:
>> > You have to allow portage to emerge/upgrade dev-libs/ilbc-rfc3951 which
>> > is masked and you have installed in past.
>> >
>> > Just add it to package.keywords like my sylpheed-claws:
>>
>> Usually an emerge would stall until a masked package is unmasked, but
>> relevant entries in /etc/portage/* files. On this occasion an emerge
>> update does not seem to try to install dev-libs/ilbc-rfc3951, it just
>> mentions that atom error. The emerge update continues fine thereafter.
>
> Found it! I had entered:
> =dev-libs/ilbc-rfc3951-0 ~x86
> in my /etc/portage/package.keywords and this package has now been revised
> to -r1 for unstable.
I believe the suggested entry in package.keywords would have been
~dev-libs/ilbc-rfc3951-0 ~x86
(initial ~ instead of =) so that the specification includes version
bumps (null --> -r1 --> -r2 ---> ...)
allan
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2006-07-17 21:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-17 9:05 [gentoo-user] Update world message Mick
2006-07-17 9:27 ` Arnau Bria
2006-07-17 10:19 ` Mick
2006-07-17 21:02 ` Mick
2006-07-17 21:29 ` Allan Gottlieb [this message]
2006-07-17 21:46 ` Mick
2006-07-17 22:58 ` Allan Gottlieb
2006-07-17 21:31 ` Neil Bothwick
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=yu9hd1f2a4m.fsf@nyu.edu \
--to=gottlieb@nyu.edu \
--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