Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 305009 - xfce-base/xfconf-4.7.2 ebuild fails
Summary: xfce-base/xfconf-4.7.2 ebuild fails
Status: RESOLVED DUPLICATE of bug 41124
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: XFCE Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-14 01:41 UTC by Ivan Trombley
Modified: 2010-02-14 07:45 UTC (History)
0 users

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


Attachments
Build log (build.log,7.41 KB, text/plain)
2010-02-14 01:43 UTC, Ivan Trombley
Details
emerge --info (emerge.info,3.84 KB, text/plain)
2010-02-14 01:45 UTC, Ivan Trombley
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ivan Trombley 2010-02-14 01:41:51 UTC
The xfce-base/xfconf-4.7.2 ebuild fails during the configure step because it can't find the XML::Parser perl module.

Reproducible: Always
Comment 1 Ivan Trombley 2010-02-14 01:43:19 UTC
Created attachment 219557 [details]
Build log
Comment 2 Ivan Trombley 2010-02-14 01:45:05 UTC
Created attachment 219559 [details]
emerge --info
Comment 3 Jeremy Olexa (darkside) (RETIRED) archtester gentoo-dev Security 2010-02-14 02:45:00 UTC
Hi,
xfconf depends on intltool, intltool depends on XML-Parser. So, the ebuild is fine and rather it is your system that is broken. If you just upgraded perl, be sure to remerge perl packages (perl-cleaner). Otherwise try: 'emerge -1 dev-perl/XML-Parser'

*** This bug has been marked as a duplicate of bug 41124 ***
Comment 4 Ivan Trombley 2010-02-14 07:45:07 UTC
(In reply to comment #3)
> Hi,
> xfconf depends on intltool, intltool depends on XML-Parser. So, the ebuild is
> fine and rather it is your system that is broken. If you just upgraded perl, be
> sure to remerge perl packages (perl-cleaner). Otherwise try: 'emerge -1
> dev-perl/XML-Parser'
> 
> *** This bug has been marked as a duplicate of bug 41124 ***
> 

Yup, that solved it. Thanks.