How can I solve all these upgrade problems? [solved]

GWilliam · Apprentice Joined: 29 Dec 2005 Posts: 294

Sorry for the ambiguity in the subject line, but there's no... I don't know. I'm just very, very, VERY tired.

I'm running the AMD64 version of Gentoo. I've been doing an emerge --sync, an emerge -uDN world (always using --pretend first!), with an occassional fixpackages and revdep-rebuild about twice a week. I've kept the system up to date and I've not had any problems with broken packages, screwed up dependencies, library versions, etc. It's been a clean and consistent system for a while now.

That all changed a couple of days ago. My system is now almost totally jacked up thanks to a recent update. I saw that there were updates to KDE and Gnome, so I knew my system would soon be happily careering down a convoluted path to self destruction, but what am I gonna do? This has always been the hallmark of the Gentoo experience for me, so it's not as if I'm not used to it, but geez...

At first, there were package blocking problems--nothing major--just blocking caused by kdesktop, ksync, and fluxconf, which I simply unmerged using emerge -C. Easily solved.

After solving the blocking problems, emerge emerge -uDN world failed because of some problem allegedly related to a Perl XML parser I think--I hardly remember at this point) but which was actually caused by something else. I think I solved the problem by unmerging and re-emerging dev-perl/XML-Parser. At any rate, the problem was solved and I could continue with my emerge -uDN world--and my descent into the unholy quagmire I'm in now.

I started emerge -uDN world again. The system cranked away until I hit another snag: kde-base/kdelibs-3.5.7-r2 won't compile. Bummer. Why won't it compile? I get this:

GWilliam · Apprentice Joined: 29 Dec 2005 Posts: 294

Update:

I've gone ahead and done this

nixnut · Posted: Sat Aug 11, 2007 12:44 pm Post subject:

a newer version of expat was stabled, and it is incompatible with the previous version, so you'll need to run revdep-rebuild -X. Run revdep-rebuild -p afterwards to check if anything else needs to be rebuild. In the Portage and Programming forum you'll find a number of threads about the expat update problem.
_________________
Please add [solved] to the initial post's subject line if you feel your problem is resolved. Help answer the unanswered

talk is cheap. supply exceeds demand

GWilliam · Apprentice Joined: 29 Dec 2005 Posts: 294

Yep. I was reading those posts last night.

I'm not using libexpat 2.0. Also, revdep-rebuild is a bit less help than it otherwise might be, what with the multiple versions of the same package getting "pulled into the dependency graph".

I believe that I may be able to solve all this on my own, although I expect it's going to take quite a long time for all the emerging and re-emerging I'll have to do.

Creating /usr/lib/libexpat.so.0 as a symlink and pointing it to /usr/lib/libexpat.so.1.5.2 has restored quite a bit of functionality (KDE and Gnome applications now work!), I have been able to compile QT 3 successfully (thanks to that symbolic link), I've just successfully compiled kdelibs, and it looks as if I might be able to finish emerge -uDN world.

I suspect that if I can get emerge -uDN world to complete, it will solve the problem with revdep-rebuild and I'll be able to use revdep-rebuild to fix what need fixin'.

However, was creating that symbolic link a bad idea? Nobody else seems to have done this to solve their upgrade problems, but their upgrade problems seem to have run a different course than mine. Was creating /usr/lib/libexpat.so.0 as a symlink and pointing it to /usr/lib/libexpat.so.1.5.2 a mistake? And why didn't I have libexpat.so.0 in the first place?

Carlo · Developer Joined: 12 Aug 2002 Posts: 3351

Hu · Veteran Joined: 06 Mar 2007 Posts: 2595

GWilliam: libexpat.so.* are part of dev-libs/expat. As nixnut said, a new version was marked stable. I suspect Portage upgraded it without you noticing. If so, you did have a libexpat.so.0 before the upgrade, which is why your programs were functional. Run emerge -pv dev-libs/expat to see what version you have installed.

If you want to blame anybody in this, blame the upstream author who decided to change the ABI and not support parallel installation of the old and new releases. Based on Gnome-2.18, KDE.3.5.7 and expat-2.0.0 - stable soon, it looks like the Gentoo maintainers have done their best to minimize the trouble caused by this upgrade. I think that if they could have made it smoother (for example, by using slots), they would have.

jonnevers · Posted: Sat Aug 11, 2007 7:02 pm Post subject:

ojbyer

cobralgato · Apprentice Joined: 14 Sep 2005 Posts: 226

revdep-rebuild -X --library libexpat.so.0 worked for me..
_________________
x86_64

a7thson · Posted: Sun Aug 12, 2007 2:33 pm Post subject:

GWilliam · Apprentice Joined: 29 Dec 2005 Posts: 294

GWilliam · Apprentice Joined: 29 Dec 2005 Posts: 294

While continuing the emerge -uDN world, emerge stopped 'cause totem-2.18.2 wouldn't compile. And why was that? Because it gnome-icon-theme requires >= 2.15.90, I have gnome-icon-theme 2.18.0, but the ebuild script seems to think I have version 2.10.1:

GWilliam · Apprentice Joined: 29 Dec 2005 Posts: 294

Oh--I should have included this--this is just before the make errors:

nightmorph · Developer Joined: 23 Jan 2005 Posts: 1289 Location: SoCal

revdep-rebuild -X to fix everything broken by the expat upgrade. Once that's done, you should be able to proceed with fixing/upgrading the rest of your system. See the Gnome 2.18 upgrade guide; I just added a section to the Known Issues on fixing expat, running revdep-rebuild, and other issues.
_________________
<UzzaDead> What is CONFIG_USB_MON?
<petteyg> A Jamaican USB configuration?

dirtyepic: "We have more cupholders."

GDP || GMN

ojbyer · Posted: Sun Aug 12, 2007 5:34 pm Post subject:

jonnevers · Posted: Sun Aug 12, 2007 5:39 pm Post subject:

if you have the xeffects overlay in your PORTDIR_OVERLAY variable you might want to disable it and then bring your system up to portage current. xeffects has the side effect of a kdelibs-3.5.7-r2 that is ~ARCH while portage's is ARCH, maybe other incompatibilities.

a7thson · Posted: Sun Aug 12, 2007 5:49 pm Post subject:

In rebuilding GTK+, I got to a configure error "Can't link to pango. Pango is required to build GTK+." (etc); attempting to rebuild pango failed. attempting to rebuild cairo (upon which pango and gtk+ depend) failed. I re-emerged the earlier (stable :-)

) version of expat, and if memory serves, then emerged cairo, then pango, then gtk+, then did revdep-rebuild -X, and remember doing a few more emerges based on "equery depends expat" output, including re-emerging gettext. Apologies for the lack of detail, I was quite frustrated by this point and up through early hours of the morning, just trying to "make it work again" :-S

Hu · Veteran Joined: 06 Mar 2007 Posts: 2595

leifbk · 24 Mar 2006

mope · Apprentice Joined: 23 Feb 2003 Posts: 206

leifbk · Posted: Mon Aug 13, 2007 5:50 am Post subject:

jonnevers · Posted: Mon Aug 13, 2007 7:21 am Post subject:

mope · Apprentice Joined: 23 Feb 2003 Posts: 206

GWilliam · Apprentice Joined: 29 Dec 2005 Posts: 294

Okay, here's what I did:

I unmasked Expat.

I unmerged Expat (checking to make sure all the relevant stuff really did get cleared out of /usr/lib).

I emerged Expat 2.0.1.

Lo and behold, I saw the exact warning message that I said earlier that the ebuild should display! Of course, messages like these just whiz by if you're emerging world.

With the new Expat installed, I ran revdep-rebuild.

I got a clean dependency graph, revdep-rebuild had no trouble building a list of packages to re-emerge.

While revdep-rebuild was re-emerging packages, it failed while trying to emerge GTK+, with the following error:

GWilliam · Apprentice Joined: 29 Dec 2005 Posts: 294