Summary: | dev-perl/MP3-Info-1.240.0-r1 :CPAN::Meta::YAML 0.011 is not available | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Toralf Förster <toralf> |
Component: | [OLD] Development | Assignee: | Gentoo Perl team <perl> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | emerge log |
Description
Toralf Förster
2015-03-13 11:54:40 UTC
Every time you get "CPAN::Meta::YAML 0.011 is not available at /usr/lib64/perl5/5.20.1/CPAN/Meta.pm line 613." That's a problem with CPAN/Meta deps. Because it says "CPAN::Meta cant be used" -> CPAN meta is broken somehow -> I'm pretty sure its the same bug. As to *why* its happening, we still haven't been able to sit down and dedicate time to working out what is going on here. Here's the exact context that error is comming from: https://metacpan.org/source/DAGOLDEN/Parse-CPAN-Meta-1.4414/lib/Parse/CPAN/Meta.pm#L57 So at best, if this is not a dup of the other one for cause, then what you'd be looking for is whatever version of Parse-CPAN-Meta you have installed not depending on >=virtual/perl-CPAN-Meta-YAML-0.11.0 Further digging: We have no version of perl-core/Parse-CPAN-Meta which would ship code that would say ""CPAN::Meta::YAML 0.011 is not available". Which means you must have the Parse/CPAN/Meta.pm that shipped with perl 5.20.* And then for your failure conditions to occur, you must also have installed perl-core/CPAN-Meta-YAML-0.8.0 ( this would be acceptable if you had a perl-core/* version of Parse-CPAN-Meta , but you do not, thus, having perl-core/CPAN-Meta-YAML installed at all is a bug ) And for this to be true, you must also have virtual/perl-CPAN-Meta-YAML-0.8.0 installed, as all other versions of that virtual indicate to remove perl-core/CPAN-Meta-YAML However, there is no path from MP3-Info to that virtual. So, to repro: 1. Install perl 5.20.* 2. Somehow install perl-core/CPAN-Meta-YAML directly (This is wrong) 3. Install dev-perl/MP3-Info #3 has no dependency chain that guarantees its safe installation. MP3-Info *could* depend on virtual/perl-ExtUtils-MakeMaker And virtual/perl-ExtUtils-MakeMaker *could* depend on virtual/perl-CPAN-Meta And that would in turn make sure you had the right version of CPAN::Meta::YAML ( But frankly, I'm up to my tits in these virtual shenanigans and I want to kill them -_- ) *** This bug has been marked as a duplicate of bug 542116 *** (In reply to Kent Fredric from comment #3) ok, so as a step toward should I mask "perl-core/CPAN-Meta-YAML" at my tinderbox to avoid such issues ? That may help you in future. I would do: <perl-core/CPAN-Meta-YAML-0.12.0 <virtual/perl-CPAN-Meta-YAML-0.12.0 However, whether or not portage will automatically *do* anything about this mask when it needs to is a different question. Because portage may very well simply not ever see that module being masked in the process of resolving the dependency tree for a package ( such as MP3-Info ). Because as far as portage is concerned ( at least, based on how it is behaving in your case ), perl-core/ is not in the dependency tree, so its not considering whether or not it should be removed. ( And that leaves us back at the same problem. ) I would simply make a habit of (appropos of) `emerge -C perl-core/*` stuff at some early stage in tinderbox generation, and then keep a very careful eye on any perl-core/* that get installed afterwards, and track *what* is installing them. |