Re: [gentoo-user] stable/testing system requiring an *UNstable* dev-lang/perl

[Alan McKinnon]

On 09/07/2014 00:33, gottlieb@×××.edu wrote:
> On Tue, Jul 08 2014, Neil Bothwick wrote:
>
>> On Tue, 08 Jul 2014 18:02:56 -0400, gottlieb@×××.edu wrote:
>>
>>> For some reason my mostly-stable-slightly-testing system
>>> is trying to merge *UNstable* dev-lang/perl.
>>
>>> Specifically it wants me to unmask
>>> =dev-lang/perl-5.20.0-r1
>>
>> That's not testing, it's masked.
>
> Right; that is what I thought I said.  Oh now I see I wrote *UNstable*.
> I thought that was a synonym for masked.  Will purge that term from my
> gentoo vocabulary.
>
>> % eix -e perl
>> [I] dev-lang/perl
>>      Available versions:  5.16.3(0/5.16) (~)5.18.2-r1(0/5.18){tbz2}
>>      [M](~)5.20.0-r1(0/5.20) {berkdb debug doc gdbm ithreads}
>>
>>> [nomerge       ] perl-core/CPAN-Meta-2.132.510
>>> [ebuild     U ~]  virtual/perl-File-Temp-0.230.400-r1 [0.230.400] 0 kB
>>> [ebuild     U  ]  virtual/perl-File-Spec-3.400.0-r1 [3.400.0] 0 kB
>>> [ebuild  r  U #]  dev-lang/perl-5.20.0-r1:0/5.20 [5.16.3:0/5.16]
>>
>> It would appear that CPAN-Meta is the culprit, see what is pulling
>> that in.
>
> That was listed in the voluminous emerge output.  Here is the relevant
> portion.  It starts with xdg-utils (required by lots) and then a
> bunch of perl.
>
> The following mask changes are necessary to proceed:
>  (see "package.unmask" in the portage(5) man page for more details)
> # required by virtual/perl-ExtUtils-Command-1.180.0-r1
> # required by perl-core/ExtUtils-MakeMaker-6.820.0
> # required by virtual/perl-ExtUtils-MakeMaker-6.820.0
> # required by perl-core/CPAN-Meta-2.132.510
> # required by virtual/perl-CPAN-Meta-2.132.510
> # required by perl-core/Module-Build-0.400.700
> # required by virtual/perl-Module-Build-0.400.700
> # required by dev-perl/File-MimeInfo-0.170.0
> # required by x11-misc/xdg-utils-1.1.0_rc2[perl]
> # required by www-client/chromium-35.0.1916.153
> # required by @selected
> # required by @world (argument)
>
>
>>> # Masked for testing, will defenitely cause major breakage
>>> # Single modules with 5.20 versions added here too -dilfridge
>>> =dev-lang/perl-5.20.0-r1
>>
>> See, masked, not keyworded, and apparently with good reason.
>
> Right.  Sorry for the masked / *UNstable* confusion.
> I was surprised eix doesn't even show this version, but that is minor.


I rather suspect you are falling foul of portage's recent weird and
wonderful behaviour trying to satisfy deps[1]. Faling that, you might
just have gotten a bad sync while someone was adding perl-5.20 to the tree

Plus your eix does not match emerge, meaning you have recently sync'ed
and not run eix-update after.

Sync again and re-run emerge -avuND world, see if the latest tree has
your issue fixed.

If not, run it with --backtrack=0 and again with --backtrack=100, let's
see if helping portage out makes a difference.

Finally, my favourite trick to find settings I forgot about:

egrep -ir "perl|cpan" /etc/portage



[1] yes, it is getting better as we move forward. But the console output
is still odd at times, it's still slow as molasses, and it really looks
like sometimes it's way to smart for it's own good.



-- 
Alan McKinnon
alan.mckinnon@×××××.com