Upgrade to expat-2.0.x needs revdep-rebuild

alanic · n00b Joined: 13 Jan 2006 Posts: 41

just wanted everyone to know that

avatar:0:0: · n00b Joined: 26 Jun 2003 Posts: 34 Location: Poland/Wrocek

"revdep-rebuild -X" should pick up ANY missing dependencies, so please explain or give some examples?

alanic · n00b Joined: 13 Jan 2006 Posts: 41

Arfrever · Posted: Fri Aug 17, 2007 7:13 pm Post subject:

avatar:0:0: · n00b Joined: 26 Jun 2003 Posts: 34 Location: Poland/Wrocek

alanic,
are you sure that you don't have two versions of libkpgp installed? for me it's the only way to get into such troubles.

datenwolf · n00b Joined: 01 Sep 2003 Posts: 55

I think symlinking libexpat.so.1.5.1 -> libexpat.so.0 should be safe for now. Expat is written in pure C, so the only ABI there is is the C ABI which hasn't changed for decades. This is unlike C++, where name mangling rules and the way templates are dealt with are changed oftenly.

AFAIK Expat-2 has been designed with API compatibility in mind (this is also written on the Expat homepage). Being a pure C library this means, that all functions whose prototype hasn't changed will be binary compatible.

So? What ABI change is there? Please give me an exact awnser like "functions are now not longer stdcall-ed but fastcall-ed" or "parameters for function xxx have changed" or similair.

As long as the dynamic linker doesn't complain about unresolved symbols I don't see a problem in symlinking the library until all dependencies have been updated. This is the great thing about pure C, you can safely mix compilers and pure C libraries, it won't break as long as you don't use fancy compiler specific stuff.

alanic · n00b Joined: 13 Jan 2006 Posts: 41

gnac · Posted: Sat Aug 18, 2007 3:33 am Post subject:

FWIW, it looks like the digikam ebuild needs to be modified to reflect the dependency on expat.

I ran revdep-rebuild and allowed it to fix what it found, but digikam still gives me a no libexpat.so.0 error. I am manually rebuilding digikam as we speak so hopefully that will fix it.

Currently (pre-digikam rebuild) revdep-rebuild gives the following output indicating breakage of kmymoney, but doesn't actually try to build anything?

spankmygentoo · n00b Joined: 20 Jun 2005 Posts: 39 Location: Utah

It worked for me, and I also deleted some games/files that were taking up space. I was at 100% capacity on the drive. Doh! Lucky for me I have ssh set up on the desktop so I just ssh'd into it from my iBook. It's all fixed now! Thanks!
_________________
--Time moves forward, whether or not you do.

maverick256 · Posted: Sat Aug 18, 2007 4:59 am Post subject:

Man, all this compiling took a day to sort out. But it's sorted out. I always wonder, perhaps it might be useful to put all the warning/info messages of all the packages to be compiled upfront, so the user can read them before deciding to emerge? But maybe I just need to get into the habit of reading the logs more.

alanic · n00b Joined: 13 Jan 2006 Posts: 41

datenwolf · n00b Joined: 01 Sep 2003 Posts: 55

I'd like to mention, that revdep-rebuild will probably report more broken binaries, as there really are. revdep-rebuild internally uses the ldd tool to determine, which libraries a program requires.

However ldd displays what libraries a program needs to be executed, NOT what libraries it directly depends on. Say A and B are libaries (A.so, B.so), B uses functionality of A and is thus B.so is linked against A.so. Now say executable C links against B.so. To be executed the dynamic linker has to load A.so and B.so, which ldd reports so.

Now say A.so gets changed and revdep-rebuild-ed. revdep-rebuild will report that C needs to be rebuilt, but actually it is B only that needs to be rebuilt.

ldd can report such dependency trees when invoked with -v mode, but from what I've seen in the revdep-rebuild code this is not used.

I think the best strategy would be to temporarily symlink libexpat.so.0 (it's a pure C library so this is one of the few cases where this doesn't hurt) and let the dependencies on it slowly dribble out of the system as things get updated.

transpetaflops · Apprentice Joined: 16 May 2005 Posts: 159

I'm in the middle of an emerge -uDN world now which seems to be working now after creating that symlink. Should I NOT remove that symlink after I complete the upgrade?

santaclaws · Posted: Sat Aug 18, 2007 1:50 pm Post subject:

I do still have some annoying problems with revdep-rebuild, besides I used the correct way to upgrade expat. (I mean no stupid symlinks, etc).

But still this output appears each time when using revdep-rebuild and I do not know how to solve it although my system is running stable.

Any suggestions, please?

I refer to that help written by kerneloftruth: https://forums.gentoo.org/viewtopic-t-573412-highlight-opal.html

kernelOfTruth · Posted: Sat Aug 18, 2007 1:53 pm Post subject:

now that looks like a mess :lol:

try emerge -e system , then execute revdep-rebuild again and see if it works better

you eventually need to unmask latest portage / gentoolkit / gentoolkit-dev
_________________
https://github.com/kernelOfTruth/ZFS-for-SystemRescueCD/tree/ZFS-for-SysRescCD-4.9.0
https://github.com/kernelOfTruth/pulseaudio-equalizer-ladspa

Hardcore Gentoo Linux user since 2004

santaclaws · Posted: Sat Aug 18, 2007 2:00 pm Post subject:

kernelOfTruth · Posted: Sat Aug 18, 2007 2:08 pm Post subject:

wait wait

then try equery b library.so.1 (whatever)

for every file which can't be linked to any package

then emerge those packages, no need for an emerge -e system :wink:

just thought you have a "fast" / up-to-date system
_________________
https://github.com/kernelOfTruth/ZFS-for-SystemRescueCD/tree/ZFS-for-SysRescCD-4.9.0
https://github.com/kernelOfTruth/pulseaudio-equalizer-ladspa

Hardcore Gentoo Linux user since 2004

santaclaws · Posted: Sat Aug 18, 2007 2:15 pm Post subject:

Captain Newbie · Apprentice Joined: 22 Dec 2006 Posts: 182 Location: Socal

gnac · Posted: Sat Aug 18, 2007 5:31 pm Post subject:

So I'm still not sure why, after rebuilding expat, running revdep-rebuild -X and revdep-rebuild -X --library=libexpat.so.0 and rebuilding digikam, I am still getting the missing libexpat error when trying to run digikam?

I am currently rebuilding anything with a lib, a dev or a sys in

alanic · n00b Joined: 13 Jan 2006 Posts: 41

extraketchup · n00b Joined: 21 Jun 2004 Posts: 29 Location: Maine

I'm usually a Gentoo Fan, BUT it's things like this that really make me mad and frustrated. I was doing what should have been a simple a quick update, only to find out it ended up breaking the system and now I need to do all this tedious voodoo to make things work again. Surely there has to be a better way to handle these kinds of library updates. At the very least, Portage should warn us with a "WARNING - if you proceed with this emerge it will take a lot longer than normal and will require you to jump through 1000 hoops to get your system working again! Are you sure you want to do that right now?"

Anyone else feel my frustration?
_________________
There are more things in heaven and earth, Horatio, Than are dreamt of in your philosophy.

gnac · Posted: Sat Aug 18, 2007 6:14 pm Post subject:

oh, thats simple enough. /sarcasm

Alanic, thanks for the info, but I do have to echo extraketchups sentiments.

This upgrade process still seams broken to me if a user has to go through this much effort to upgrade an "unmasked", un keyworded package.
_________________
"I thought she'd steal my heart, instead she stole my kidney,
and now its for sale, on the black market in Sydney" - Better Abraham

kernelOfTruth · Posted: Sat Aug 18, 2007 6:17 pm Post subject:

alanic · n00b Joined: 13 Jan 2006 Posts: 41

well it didn't take me too long to get rid of this. Now I think we all did something wrong to get ourselves into this mess, normally when it updates something it should make sure it's updating other stuff that depends on the updated package. I think it's the -D option that opens the gates to hell.
(See I learned someting today;) )