Bugzilla Bug 149634

>>> Source compiled.
>>> Test phase [not enabled]: x11-themes/gnome-icon-theme-2.16.0.1

>>> Install gnome-icon-theme-2.16.0.1 into /var/tmp/portage/gnome-icon-theme-2.16.0.1/image/ category x11-themes
Making install in 8x8
make[1]: Entering directory
`/var/tmp/portage/gnome-icon-theme-2.16.0.1/work/gnome-icon-theme-2.16.0.1/8x8'
Making install in emblems
make[2]: Entering directory
`/var/tmp/portage/gnome-icon-theme-2.16.0.1/work/gnome-icon-theme-2.16.0.1/8x8/emblems'
make[3]: Entering directory
`/var/tmp/portage/gnome-icon-theme-2.16.0.1/work/gnome-icon-theme-2.16.0.1/8x8/emblems'
make[3]: Nothing to be done for `install-exec-am'.
test -z "/usr/share/icons/gnome/8x8/emblems" || mkdir -p --
"/var/tmp/portage/gnome-icon-theme-2.16.0.1/image//usr/share/icons/gnome/8x8/emblems"
/bin/install -c -m 644 'emblem-new.png'
'/var/tmp/portage/gnome-icon-theme-2.16.0.1/image//usr/share/icons/gnome/8x8/emblems/emblem-new.png'
 /bin/install -c -m 644 'emblem-symbolic-link.png'
'/var/tmp/portage/gnome-icon-theme-2.16.0.1/image//usr/share/icons/gnome/8x8/emblems/emblem-symbolic-link.png'
(cd /var/tmp/portage/gnome-icon-theme-2.16.0.1/image//usr/share/icons/gnome/8x8
&& /usr/libexec/icon-name-mapping -c emblems)
Can't locate object method "new" via package "XML::LibXML::SAX::Parser" at
/usr/lib/perl5/vendor_perl/5.8.8/XML/SAX/ParserFactory.pm line 43.
make[3]: *** [install-data-local] Error 2
make[3]: Leaving directory
`/var/tmp/portage/gnome-icon-theme-2.16.0.1/work/gnome-icon-theme-2.16.0.1/8x8/emblems'
make[2]: *** [install-am] Error 2
make[2]: Leaving directory
`/var/tmp/portage/gnome-icon-theme-2.16.0.1/work/gnome-icon-theme-2.16.0.1/8x8/emblems'
make[1]: *** [install-recursive] Error 1
make[1]: Leaving directory
`/var/tmp/portage/gnome-icon-theme-2.16.0.1/work/gnome-icon-theme-2.16.0.1/8x8'
make: *** [install-recursive] Error 1

!!! ERROR: x11-themes/gnome-icon-theme-2.16.0.1 failed.
Call stack:
  ebuild.sh, line 1546:   Called dyn_install
  ebuild.sh, line 1020:   Called src_install
  ebuild.sh, line 1255:   Called gnome2_src_install
  gnome2.eclass, line 77:   Called die

!!! install failed
!!! If you need support, post the topmost build error, and the call stack if
relevant.


And my emerge --info:
Portage 2.1.1 (default-linux/x86/no-nptl, gcc-4.1.1, glibc-2.3.6-r4,
2.6.17-gentoo-r7 i686)
=================================================================
System uname: 2.6.17-gentoo-r7 i686 AMD Athlon(tm) XP 2000+
Gentoo Base System version 1.12.5
Last Sync: Sat, 30 Sep 2006 14:20:01 +0000
app-admin/eselect-compiler: [Not Present]
dev-java/java-config: 1.3.7, 2.0.30
dev-lang/python:     2.4.3-r4
dev-python/pycrypto: 2.0.1-r5
dev-util/ccache:     [Not Present]
dev-util/confcache:  [Not Present]
sys-apps/sandbox:    1.2.17
sys-devel/autoconf:  2.13, 2.59-r7
sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2
sys-devel/binutils:  2.16.1-r3
sys-devel/gcc-config: 1.3.13-r3
sys-devel/libtool:   1.5.22
virtual/os-headers:  2.6.17-r1
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CBUILD="i686-pc-linux-gnu"
CFLAGS="-O2 -march=athlon-xp -pipe -fomit-frame-pointer"
CHOST="i686-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/share/X11/xkb"
CONFIG_PROTECT_MASK="/etc/env.d /etc/env.d/java/ /etc/gconf
/etc/java-config/vms/ /etc/revdep-rebuild /etc/splash /etc/terminfo"
CXXFLAGS="-O2 -march=athlon-xp -pipe -fomit-frame-pointer"
DISTDIR="/usr/distfiles"
FEATURES="autoconfig ccache distlocks parallel-fetch sandbox sfperms strict"
GENTOO_MIRRORS="ftp://gentoo.po.opole.pl/ http://gentoo.prz.rzeszow.pl/
ftp://ftp.sh.cvut.cz/MIRRORS/gentoo/"
LC_ALL="pl_PL.UTF-8"
LINGUAS="pl en"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress
--force --whole-file --delete --delete-after --stats --timeout=180
--exclude='/distfiles' --exclude='/local' --exclude='/packages'"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage /usr/portage/local/layman/sunrise"
SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage"
USE="x86 3dnow 3dnowext X aac acpi alsa apm artworkextra asf audiofile avi
bash-completion berkdb bitmap-fonts bzip2 cairo cdr cli crypt cups curl dbus
divx4linux dlloader dri dvd dvdr dvdread eds elibc_glibc emboss encode esd
extras fam fbcon firefox flac foomaticdb fortran gd gdbm gif gnome gpm
gstreamer gtk gtk2 gtkhtml hal howl imlib input_devices_keyboard
input_devices_mouse isdnlog java jpeg kernel_linux lcms libg++ libwww
linguas_en linguas_pl lirc lirc_devices_devinput mad matroska mikmod mmx mmxext
motif mp3 mpeg musepack nautilus ncurses nls nntp nvidia ogg opengl oss pam
pcre perl png pppd python qt qt3 qt4 quicktime readline reflection reiserfs
ruby sdl session spell spl sqlite sse ssl symlink tcltk tcpd threads tiff
truetype truetype-fonts type1-fonts unicode usb userland_GNU v4l v4l2 vcd
video_cards_none video_cards_nvidia vorbis win32codecs xcomposite xine xml xorg
xv xvid zlib"
Unset:  CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LDFLAGS,
PORTAGE_RSYNC_EXTRA_OPTS

CONFIRMED

REASON:
x11-misc/icon-naming-utils-0.8.1 needs RDEPEND dev-perl/XML-LibXML.
gnome-icon-theme-2.16.0.1 emerged successfully with XML-LibXML-1.58-r1

yep, now it compiles without any errors.

Reopening because I don't see any such DEP or RDEP (shouldn't it be DEP rather
than RDEP?) having been added to the ebuild.
I haven't verified this personally yet.

This does not appear to be a problem with icon-naming-utils.  It only
references XML::Simple, which is already a dep.

Adding perl to see if they have any ideas.

XML::Simple uses XML::SAX which picks its parser using this file:
/usr/lib/perl5/vendor_perl/5.8.8/XML/SAX/ParserDetails.ini

So I assume stemer installed XML::LibXML, removed it, and ParserDetails.ini
wasn't updated.

Stemer, as root, run the following line:
perl -MXML::SAX -e
"XML::SAX->add_parser(q(XML::SAX::PurePerl))->save_parsers()"
It Should Work (TM).

I guess we should issue this command whenever unmerging XML-LibXML or any other
XML::SAX parser...

Ugh, stemer, a better command would be:
perl -MXML::SAX -e
"XML::SAX->remove_parser(q(XML::LibXML::SAX::Parser))->save_parsers()"

Pasted the wrong line (i.e., the one from the XML::SAX FAQ) by accident.
It'll work, but it won't remove XML::LibXML::SAX::Parser from the list, just
put XML::SAX::PurePerl at the top of it :)

Then XML::Simple should dep on XML::SAX, yes?  Nothing for gnome-icon-theme to
do here.

Nope, IIRC XML::Simple uses XML::SAX only if it's installed.

Actually, I've contacted stemer on irc, and we both can't reproduce it.
He had a chroot (stemer, I don't really remember the setup, could you
elaborate?), I'm suspecting XML::SAX took the settings from somewhere else
(either the file out side the chroot [if he wasn't chrooted at the time], and
there's also the environment variable thingie...)

Since both stemer and I can't reproduce it, I say (and stemer agreed :)) that
it should be WORKSFORME or INVALID until someone is able to reproduce it.

Okay, I would tend to agree.  It certainly doesn't seem to be a
gnome-icon-theme problem, so I'll re-assign to perl, and you can resolve
however you feel is best.  Is this the kind of thing that perl-cleaner would
fix?

hi, yup - just WORKSFORME.

It has nothing to do with perl-cleaner...
Bug looks like it comes from x11-misc/icon-naming-utils, btw.

same problem with gnome-icon-theme-2.16.1

Sorry, forgot to say that this solution worked for me too :)

*** Bug 157004 has been marked as a duplicate of this bug. ***

Still happen with x11-themes/gnome-icon-theme-2.16.1

(In reply to comment #13)
> Sorry, forgot to say that this solution worked for me too :)

which solution worked for you ? If any fix was done in ebuild, souldn't it be
synched by now ? (esynced again 'now' to make sure before validating bug).

Please re-open.

(In reply to comment #15)
> Still happen with x11-themes/gnome-icon-theme-2.16.1
> 
> (In reply to comment #13)
> > Sorry, forgot to say that this solution worked for me too :)
> 
> which solution worked for you ? If any fix was done in ebuild, souldn't it be
> synched by now ? (esynced again 'now' to make sure before validating bug).
> 

The one reported in comment #6 . the line starting with perl -e and finishing
with save_parsers()"

*** Bug 157244 has been marked as a duplicate of this bug. ***

Please reopen.  This fails for me. (version 2.16.2). (I filed the bug Bug
157244, which is now marked as duplicate of this).

Stumbled upon bug 157004 which is duped here.

This bug here can be caused by bug 157119 resulting in an empty LibXML
installation.

BTW: shouldn't ParserDetails.ini be config-protcted, so you would not have to
remerge other parser implementations?

(In reply to comment #17)
> > which solution worked for you ?
> The one reported in comment #6 .

Yes this worked for me; still, "because it requires human interaction", I can
not consider this issue solved at the distro level: until every single user hit
this line, more people will encontour the problem. I dont think expecting every
user to come and erad this bug is acceptable. I still ask for an upgrade of
ebuild.

Cheers.

Same problem around here with gnome-themes 2.16.2.

perl -MXML::SAX -e
"XML::SAX->remove_parser(q(XML::LibXML::SAX::Parser))->save_parsers()"

worked for me too ;)

Thx yuvvy !

I can confirm that this problem still exists with
x11-themes/gnome-icon-theme-2.16.1
For me this bug has to be REOPENED.

can someone explain why the bug has not been reopened?  All we have now is a
temporary workaround for users who find it on bugzilla, yes?  It seems ebuilds
have not been fixed, right?

Shouldn't this bug be reopened??

Yes, it should. But the ones who have power on this do not do so. Most often,
the ones who have power on this are not even CC of bugs, so, they are not
notified users are not happy.

We all say the same in #21 #23 and #24.

*** Bug 158108 has been marked as a duplicate of this bug. ***

*** Bug 158221 has been marked as a duplicate of this bug. ***

Re-opening because more people are hitting this again...

Downgrading to dev-perl/XML-SAX-0.13 (by putting 0.14-r1 in package.mask) will
circumvent the problem until a fix is provided.

This was fixed in the XML-SAX ebuild already.


pkg_postinst() {
        perl-module_pkg_postinst
        perl -MXML::SAX \
                -e
"XML::SAX->add_parser(q(XML::SAX::PurePerl))->save_parsers()" \
                || die "error adding parser"
}

*** Bug 203828 has been marked as a duplicate of this bug. ***

I just reproduced the bug with gnome-icon-themes-2.22.0. Indeed, 

perl -MXML::SAX -e
"XML::SAX->remove_parser(q(XML::LibXML::SAX::Parser))->save_parsers()" 

fixed the problem, but I wonder why it happened in the first place since I have
XML-SAX-0.16 emerged, and the ebuild contains

pkg_postinst() {
        perl-module_pkg_postinst
        perl -MXML::SAX \
                -e
"XML::SAX->add_parser(q(XML::SAX::PurePerl))->save_parsers()" \
                || die "error adding parser"
}

(In reply to comment #32)
> "XML::SAX->remove_parser(q(XML::LibXML::SAX::Parser))->save_parsers()" 
> fixed the problem, but I wonder why it happened in the first place
> since I have XML-SAX-0.16 emerged, and the ebuild contains
> "XML::SAX->add_parser(q(XML::SAX::PurePerl))->save_parsers()"

The parser list (/usr/lib/perl5/vendor_perl/*/XML/SAX/ParserDetails.ini) can
contain multiple parsers. So I assume in your case that it does include both
LibXML and PurePerl, and the application deems LibXML to be suited better. As
this doesn't work, I assume your instalation of dev-perl/XML-LibXML is either
somehow broken or removed altogether. It seems like XML-LibXML doesn't properly
uninstall on removal, for which I just filed bug 235502.

*** Bug 289181 has been marked as a duplicate of this bug. ***

Same problem with gnome-icon-theme-2.26.0 but the perl command in comment #6
did not resolve this issue for me. Please consider reopening this bug.

(In reply to comment #35)
> Same problem with gnome-icon-theme-2.26.0 but the perl command in comment #6
> did not resolve this issue for me. Please consider reopening this bug.

No. Please file a new bug. Attach your emerge --info.
Tell us which perl, dev-perl/XML-LibXML, dev-perl/XML-SAX versions you are
using and what you did before this happens.
What is in your ParserDetails.ini ?