From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] perl versioning problem, how to get beyond for @world
Date: Tue, 15 May 2012 01:21:44 +0200 [thread overview]
Message-ID: <20120515012144.1d16fe44@khamul.example.com> (raw)
In-Reply-To: <87pqa6pdyi.fsf@newsguy.com>
On Mon, 14 May 2012 18:58:29 -0400
Harry Putnam <reader@newsguy.com> wrote:
> I have a light minimalish system (noX) and not a lot installed but
> for a the last few weeks, when I try to update with emerge -vuD world
>
> It caves about a perl versioning problem, and specifically about:
> perl-core/Module-Build-0.400.0
>
> Abbreviated output:
> ,----
> | >>> Emerging (1 of 12) perl-core/Module-Build-0.400.0
> | * Module-Build-0.40.tar.gz RMD160 SHA1 SHA256
> size ;-) ... | [ ok ]
> | >>> cfg-update-1.8.2-r1: Checksum index is up-to-date ...
> | >>> Unpacking source...
> | >>> Unpacking Module-Build-0.40.tar.gz to
> | /var/tmp/portage/perl-core/Module-Build-0.400.0/work
> | >>> Source unpacked
> in /var/tmp/portage/perl-core/Module-Build-0.400.0/work | >>>
> Preparing source in
> | /var/tmp/portage/perl-core/Module-Build-0.400.0/work/Module-Build-0.40 ...
> | >>> Source prepared. | >>> Configuring source in
> | /var/tmp/portage/perl-core/Module-Build-0.400.0/work/Module-Build-0.40 ...
> | * Using Module::Build
> | * perl Build.PL --installdirs=vendor --libdoc=
> | --destdir=/var/tmp/portage/perl-core/Module-Build-0.400.0/ima
> | ge/ --create_packlist=0
> | *** BOOTSTRAPPING version ***
> | 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.
Does unmerging and remerging Parse-CPAN-Meta fix anything?
--
Alan McKinnnon
alan.mckinnon@gmail.com
next prev parent reply other threads:[~2012-05-14 23:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-14 22:58 [gentoo-user] perl versioning problem, how to get beyond for @world Harry Putnam
2012-05-14 23:21 ` Alan McKinnon [this message]
2012-05-18 1:03 ` [gentoo-user] " Harry Putnam
2012-05-21 18:42 ` Arttu V.
2012-05-25 18:06 ` Harry Putnam
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=20120515012144.1d16fe44@khamul.example.com \
--to=alan.mckinnon@gmail.com \
--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