Summary: | dev-perl/Config-Any fails tests | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Diego Elio Pettenò (RETIRED) <flameeyes> |
Component: | New packages | Assignee: | Gentoo Perl team <perl> |
Status: | RESOLVED OBSOLETE | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 300119 | ||
Attachments: | Build log |
Description
Diego Elio Pettenò (RETIRED)
2010-04-01 09:46:22 UTC
Created attachment 226091 [details]
Build log
> Can't locate XML/LibXML/SAX.pm in @INC
It's strange. Again an ithreads problem?
Can you confirm that you have dev-perl/XML-Simple installed and also dev-perl/XML-SAX and dev-perl/XML-LibXML?
Still it's not found?
Can you paste /usr/lib*/perl5/vendor_perl/5*/XML/SAX/ParserDetails.ini
This is during the middle of perl-cleaner to _solve_ that problem. Sigh. I guess this should depend on XML-SAX with test USE flag enabled, to tell Portage that it has to rebuild that before this one. (In reply to comment #3) > Sigh. Yeah, me too. > I guess this should depend on XML-SAX with test USE flag enabled, to tell > Portage that it has to rebuild that before this one. I think this is a workaround too. As it is not necessary to reinstall all the pure perl modules by perl-cleaner, i think we should try to implement this. Identify all perl modules with binary parts and reinstall them automatically after a useflag change of dev-lang/perl. But this something for a another bug. Agreed on the need to get this on Portage. But I don't feel it's a workaround to explicit the test dependencies of the package, after all they are needed, are they not? Wouldn't it fail if the deps are missing from the system anyway? Config-Any only deps on Module-Pluggable and afaict that does not bring in XML-SAX. (In reply to comment #5) > But I don't feel it's a workaround to explicit the test dependencies of the > package, after all they are needed, are they not? Wouldn't it fail if the deps > are missing from the system anyway? No, it doesn't fail, it just skips the tests. XML, INI, JSON, YAML are all optional. Ah I see now. Hm, that's a bit funky :( For what it's worth in Ruby I've been trying to force the tests in whenever possible, so if it was up to me I'd just add all the optional test deps as mandatory test deps… 0.19 no longer in the tree. Current version (0.230.0) works fine. |