At Mon, 17 Jul 2006 22:02:06 +0100 Mick <[EMAIL PROTECTED]> 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
--
[email protected] mailing list
