Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 289181 - x11-themes/gnome-icon-theme-2.26.0 fails to install
Summary: x11-themes/gnome-icon-theme-2.26.0 fails to install
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] GNOME (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Gentoo Perl team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: gnome2.26
  Show dependency tree
 
Reported: 2009-10-15 09:11 UTC by Marko Steinberger
Modified: 2009-11-14 20:39 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
emerge --info (emerge.info,3.99 KB, text/plain)
2009-10-15 09:12 UTC, Marko Steinberger
Details
Complete build log of portage. (build.log,50.46 KB, text/plain)
2009-10-15 09:13 UTC, Marko Steinberger
Details
Martin Swift's emerge --info (emerge-info.log,3.55 KB, text/plain)
2009-10-30 12:11 UTC, Martin Swift
Details
Output of 'qlist -e XML-LibXML' (qlist-e-XML-LibXML.log,2.42 KB, text/plain)
2009-10-31 23:58 UTC, Martin Swift
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Marko Steinberger 2009-10-15 09:11:44 UTC
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
Comment 1 Marko Steinberger 2009-10-15 09:12:22 UTC
Created attachment 207191 [details]
emerge --info

Output of emerge --info.
Comment 2 Marko Steinberger 2009-10-15 09:13:25 UTC
Created attachment 207193 [details]
Complete build log of portage.
Comment 3 Gilles Dartiguelongue (RETIRED) gentoo-dev 2009-10-21 23:38:59 UTC
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 ***
Comment 4 Martin Swift 2009-10-30 12:11:53 UTC
Created attachment 208729 [details]
Martin Swift's emerge --info
Comment 5 Martin Swift 2009-10-30 12:18:48 UTC
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
Comment 6 Gilles Dartiguelongue (RETIRED) gentoo-dev 2009-10-30 12:30:27 UTC
ok, reopening then
Comment 7 Gilles Dartiguelongue (RETIRED) gentoo-dev 2009-10-30 12:30:43 UTC
and move to perl herd.
Comment 8 Torsten Veller (RETIRED) gentoo-dev 2009-10-30 23:20:03 UTC
What did XML-LibXML install? (qlist -e XML-LibXML)
Comment 9 Martin Swift 2009-10-31 23:53:58 UTC
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?
Comment 10 Martin Swift 2009-10-31 23:56:59 UTC
(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.
Comment 11 Martin Swift 2009-10-31 23:58:15 UTC
Created attachment 208911 [details]
Output of 'qlist -e XML-LibXML'
Comment 12 Marko Steinberger 2009-11-01 16:40:14 UTC
As far as I am concerned, emerging dev-perl/XML-LibXML as mentioned in bug 149634 solved the problem.
Comment 13 David Abbott (RETIRED) gentoo-dev 2009-11-14 20:39:10 UTC
I am going to close the bug as it appears to be resolved, please reopen if needed.