This package (version 2.24.0) was installed as dependency by current testing package "mysql-gui-tools". Now, upgrading this package fails during install stage. Please note, that I have "-gnome" in my use flags as I use kde. System is stable for most packages. Reproducible: Always Steps to Reproduce: 1. emerge -auND world (or emerge -a =x11-themes/gnome-icon-theme-2.26.0). Actual Results: See build.log. Expected Results: Should install
Created attachment 207191 [details] emerge --info Output of emerge --info.
Created attachment 207193 [details] Complete build log of portage.
Used search feature of bugzilla and found something that look quite similar from 2006. *** This bug has been marked as a duplicate of bug 149634 ***
Created attachment 208729 [details] Martin Swift's emerge --info
I'm having the same problem and asked that bug 149634 be re-opened. There it was requested that I open a new bug. I take ti that this is, therefore, not a duplicate. I get the same output as in the reporter's build log. emerge --info attached. Versions: * perl, v5.8.8 built for i686-linux-thread-multi * dev-perl/XML-LibXML 1.66-r1 * dev-perl/XML-SAX 0.16 $ cat /usr/lib/perl5/vendor_perl/5.8.8/XML/SAX/ParserDetails.ini [XML::SAX::PurePerl] http://xml.org/sax/features/namespaces = 1 [XML::LibXML::SAX] http://xml.org/sax/features/namespaces = 1
ok, reopening then
and move to perl herd.
What did XML-LibXML install? (qlist -e XML-LibXML)
I've just found that perl seemed not to find Parser.pm which belongs to dev-perl/XML-Parser. Reemerging that package fixed the problem (which also seemed to be breaking the compilation of sys-auth/policykit). Should this have been caught by revdep-rebuild?
(In reply to comment #8) > What did XML-LibXML install? (qlist -e XML-LibXML) This problem may be solved (see comment #9) but in case problems persist, I'm attaching the output of that command.
Created attachment 208911 [details] Output of 'qlist -e XML-LibXML'
As far as I am concerned, emerging dev-perl/XML-LibXML as mentioned in bug 149634 solved the problem.
I am going to close the bug as it appears to be resolved, please reopen if needed.