Gnome 2.18 upgrade
Posted on August 10th, 2007 by Daniel
Just a quick note. Gnome 2.18 is going stable. During the upgrade, you’ll hit this problem:
checking for XML::Parser... configure: error: XML::Parser perl module is required for intltool
This is *not* gnome’s fault, it’s the fault of the expat upgrade. The fix is to run this:
revdep-rebuild -X
This will rebuild everything broken by expat, doing upgrades as it goes. After it’s done, you should be able to finish upgrading gnome.
We tried to time the gnome and kde stabilizations to match expat so that you’d only have to rebuild tons of stuff once.
[…] But yesterday I must say I had quite a bit of fun with it. I keep to a fairly recent upgrade path, so I rarely fall behind more than a week. The expat1->2 upgrade had been in the works for some time, but the einfo flew by without me seeing it, as it often is. Interestingly, half the packages on the system depend on expat, and all of them were suddenly broken. The first thing I noticed was Firefox behaving odd. […]
revdep-rebuild -X did not do anything useful for me. It did reemerge gcc-4.1.2 and gcc-3.4.6 for the bazillionth time, but when trying to do “emerge -uD world”, aforementioned error “checking for XML::Parser… etc” persisted.
I had to check what is depending on expat with “equery depends expat” and after emerging everthing on that list “emerge -uD world” went fine…
Then your revdep-rebuild is broken. You might want to upgrade it. Interestingly, expat is viral and just using equery d expat isn’t enough to find everything that’s linked against it, usually.
I’m just upgraded gcc and hence world and everything has been working nicely, is step only necessary for some arches?
I’m using expat-2.01.
It’s needed when upgrading from expat 2. It’s needed for all arches. If you run ~arch, you did the expat upgrade a long time ago, and probably forgot the pain…