From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1SWXaA-0006DW-GH for garchives@archives.gentoo.org; Mon, 21 May 2012 18:43:50 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id A4649E0CAC; Mon, 21 May 2012 18:43:30 +0000 (UTC) Received: from mail-lb0-f181.google.com (mail-lb0-f181.google.com [209.85.217.181]) by pigeon.gentoo.org (Postfix) with ESMTP id 9AF8CE0CAB for ; Mon, 21 May 2012 18:42:04 +0000 (UTC) Received: by lbbgk8 with SMTP id gk8so4243063lbb.40 for ; Mon, 21 May 2012 11:42:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=SdqhKt+Zj1UU1kmupg4IrJGA3aHYZgil39sNZurBLIQ=; b=PPJploP+EOwT7AwSJ+inQF2NKVNn1zy4Cs7GoPd/JRgHhhp1hzOaqayZGS32uA0qOp hQMYibBFch58t/UUyj64gbU1ktfYF5IhS7PiYk8zoxOaSO2B8PbfjfzFBZVqj/0mGVlf BjUxbozlmft1BUBHxEbmiWcGGJxjhgubNXEfRr2A6R2X8vIpDPRrLF7RtkWJc/qM+/sW WkL2MBUVj5fodR0Y7u2KxYxLorOIYTTLpYeBF+k+Nn8J39yjg719dQxpJJNBSt9HBgGM GiO4m3x5KSXBAUaNJ+SLtse9sht9fmk/G94Kn0ue71iattr0QwdBCSgzFD47eXztQKS1 aZlg== Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Received: by 10.112.88.106 with SMTP id bf10mr9061143lbb.43.1337625723399; Mon, 21 May 2012 11:42:03 -0700 (PDT) Received: by 10.152.5.197 with HTTP; Mon, 21 May 2012 11:42:03 -0700 (PDT) In-Reply-To: <874nre712v.fsf@newsguy.com> References: <87pqa6pdyi.fsf@newsguy.com> <20120515012144.1d16fe44@khamul.example.com> <874nre712v.fsf@newsguy.com> Date: Mon, 21 May 2012 21:42:03 +0300 Message-ID: Subject: Re: [gentoo-user] Re: perl versioning problem, how to get beyond for @world From: "Arttu V." To: gentoo-user@lists.gentoo.org Content-Type: text/plain; charset=ISO-8859-1 X-Archives-Salt: b10c1861-dfcf-4cdd-841c-eff372883980 X-Archives-Hash: 39e61249db1bb237451e5a019d17c0b9 It looks like the @INC list (the directory list perl uses for finding its modules) is not right or is not processed right. Only one directory is looked into? (You can see @INC with "perl -V", it should be up to about ten directories on a Gentoo install.) Unless you really, really want to know exactly which bit from which package is sideways you might get out of the hole simply with: perl-cleaner --reallyall -- Arttu V. On 5/18/12, Harry Putnam wrote: > Alan McKinnon writes: > > [...] > >>> | Checking prerequisites... >>> | build_requires: >>> | ! Parse::CPAN::Meta (1.40) is installed, but we need version >= >>> | 1.4401 >>> | ERRORS/WARNINGS FOUND IN PREREQUISITES. You may wish to install >>> the versions | of the modules indicated above before proceeding with >>> this installation | >>> | Could not create MYMETA files >>> | Creating new 'Build' script for 'Module-Build' version '0.40' >>> | Copied META.yml to MYMETA.yml for bootstrapping >>> | >>> | These additional prerequisites must be installed: >>> | requires: >>> | ! version (we need version 0.87) >>> | >>> Source configured. >>> | >>> Compiling source in >>> | /var/tmp/portage/perl-core/Module-Build-0.400.0/work/Module-Build-0.40 >>> ... >>> | version version 0.87 required--this is only version 0.82 at >>> | /usr/lib/perl5/vendor_perl/5.12.4/Module/Metadata >>> | .pm line 20. >>> | [...] >>> `---- >>> >>> I can't really see what to do about this... >>> >>> What is installed is: >>> >>> ,---- >>> | # eix -Ic|grep Parse.*Meta >>> | [I] perl-core/Parse-CPAN-Meta (1.440.400@05/03/12): Parse META.yml >>> and other | similar CPAN metadata files >>> | [I] virtual/perl-Parse-CPAN-Meta (1.440.400@04/25/12): Virtual for >>> Parse-CPAN-Meta `---- >> >> Perl and any package manager tend to make an ugly combination... >> >> Now, I've never seen this specific error before but it looks like perl >> thinks your installed Parse-CPAN-Meta is still the old version 1.40. It >> doesn't realize what portage did in the interim. >> >> Have a look in that ebuild and 1.440.400 and you'll see quite a >> difference. > > Quite a difference in what? Or compared to what? > >> Does unmerging and remerging Parse-CPAN-Meta fix anything? > > I tried emerge -vC the core Parse-CPAN-Meta and the Virtual > Parse-CPAN-Meta > > Then eix-sync, then emerge -vuD world > > When it gets to building `perl-core/Module-Build-0.400.0' > > The same failure happens: > > ,---- > | [...] > | Checking prerequisites... > | build_requires: > | ! Parse::CPAN::Meta (1.40) is installed, but we need version >= > 1.4401 > | > | ERRORS/WARNINGS FOUND IN PREREQUISITES. You may wish to install the > versions > | of the modules indicated above before proceeding with this installation > | > | Could not create MYMETA files > | Creating new 'Build' script for 'Module-Build' version '0.40' > | Copied META.yml to MYMETA.yml for bootstrapping > | > | These additional prerequisites must be installed: > | requires: > | ! version (we need version 0.87) > | >>> Source configured. > | [...] > `---- > > emerge has installed two very different [...]//Parse/CPAN/Meta.pm > > ,---- > | ls -l /usr/lib/perl5/5.12.4/Parse/CPAN/Meta.pm \ > | /usr/lib/perl5/vendor_perl/5.12.4/Parse/CPAN/Meta.pm > | > | [...]10522 Apr 25 20:49 /usr/lib/perl5/5.12.4/Parse/CPAN/Meta.pm > | [...] 7582 May 11 20:13 > /usr/lib/perl5/vendor_perl/5.12.4/Parse/CPAN/Meta.pm > `---- > > And they say very different things: > > From /usr/lib/perl5/5.12.4/Parse/CPAN/Meta.pm: > > [...] > # Class structure > require 5.004; > require Exporter; > $Parse::CPAN::Meta::VERSION = '1.40'; > @Parse::CPAN::Meta::ISA = qw{ Exporter }; > @Parse::CPAN::Meta::EXPORT_OK = qw{ Load LoadFile }; > [...] > > From /usr/lib/perl5/vendor_perl/5.12.4/Parse/CPAN/Meta.pm: > > # Class structure > require 5.004; > require Exporter; > $Parse::CPAN::Meta::VERSION = '1.4404'; > @Parse::CPAN::Meta::ISA = qw{ Exporter }; > @Parse::CPAN::Meta::EXPORT_OK = qw{ Load LoadFile }; > > One looks for 1.40, the other for 1.4404 > > I don't know what the code does but, is this possibly the problem? If > so its not at all clear what to do about it. > > qfile on /usr/lib/perl5/5.12.4/Parse/CPAN/Meta.pm > Shows it comes from the main perl installation: > > qfile /usr/lib/perl5/5.12.4/Parse/CPAN/Meta.pm > ,---- > | dev-lang/perl (/usr/lib/perl5/5.12.4/Parse/CPAN/Meta.pm) > `---- > So that is from the main perl installation. > > Just renaming /usr/lib/perl5/5.12.4/Parse/CPAN/Meta.pm to > /usr/lib/perl5/5.12.4/Parse/CPAN/XMeta.pmX > > Causes a new miss match on version when building > perl-core/Module-Build-0.400.0 > ,---- > | *** BOOTSTRAPPING version *** > | Could not create MYMETA files > | Creating new 'Build' script for 'Module-Build' version '0.40' > | Copied META.yml to MYMETA.yml for bootstrapping > | > | These additional prerequisites must be installed: > | requires: > | ! version (we need version 0.87) > | >>> Source configured. > | >>> Compiling source in > /var/tmp/portage/perl-core/Module-Build-0.400.0/work/Module-Build-0.40 ... > | version version 0.87 required--this is only version 0.82 at > /usr/lib/perl5/vendor_perl/5.12.4/Module/Metadata.pm line 20. > `---- > > So it appears there is some deeper mangling somewhere. > > > >