On Tue, 11 May, 2010 at 11:43:59 -0400, John E. Perry wrote:
I just tried my second "zypper up" after switching from "zypper dup" due to the responses to my "Changing zypper command" message of last week.
Oops.
zypper: error while loading shared libraries: libzypp.so.619: cannot open shared object file: No such file or directory
Not good. As Carlos said: It would be good to know (how/why) what changed. Something like 'less /root/.bash_history' (as root) might help retrace your steps?
Now, yast won't start (dbus error), zypper won't start.
Not entirely surprising, in that both probably need libzypp.so.NNN which is not found. Looking at http://download.opensuse.org/distribution/11.2/repo/oss/suse/i586/libzypp-6.... with Konqueror's embedded KRPMview, we see that it contains libzypp.so.619 This tells us that 'zypper' most likely is the version which is contained on the install medium - since it's referencing the libzypp version from the install medium. It *might* also indicate that 'libzypp' was updated - since that would have replaced /usr/lib/libzypp.so.619 with (f.x.) /usr/lib/libzypp.so.631 (as is the case on my system which has been updated more or less continuously)
I suppose I might manually copy the library, if I knew where to get it and where to put it.
Manually copying individual library files onto the system as almost certainly not a good idea. Manually upgrading packages, however, might be.
Is there anything I can do short of reinstalling suse?
Reinstalling shouldn't be neccessary. But now might be a good time to backup whatever you have on there, in case any of the things I'm about to suggest make matters any worse ;) (In this next bit I'm just assuming the architechture is i586, so substitute x86_64 if neccessary) The first thing I'd suggest is to find out which version of libzypp is actually present on the system: rpm -q libzypp and ll /usr/lib/libzypp.so* should tell us that. Next: Depending on the outcome of the above (which I'm guessing will be that libzypp *is* present, but newer than the version from the install medium) - I would probably suggest to upgrade zypper, yast, et al. to a consistent 'level'. This would entail something like: mkdir -p /tmp/packages Then download individual rpms from: http://download.opensuse.org/update/11.2/rpm/i586/ to /tmp/packages The reason for using a directory is that you can then use: rpm --test -Uvh /tmp/packages/* - which will let rpm figure out the order to upgrade the rpms present in /tmp/packages As for which rpms to download: Well, it may take some iterations to get the dependencies sorted out, but it's probably going to be something on the order of: jon@nx8220:~> rpm -q --whatrequires libzypp zypper-1.3.4-0.1.3.i586 yast2-qt-pkg-2.18.22-1.1.1.i586 libqdialogsolver1-1.3.0-2.12.1.i586 yast2-pkg-bindings-2.18.11-1.3.1.i586 Initially though, just try with zypper-<version>.rpm, run the rpm command, and see what happens. Once rpm stops complaining about dependencies, you should be good to run the command without '--test', to actually install/upgrade the packages.
I do have the opensuse ISO's on my hard drive, but since I haven't downloaded Krusader since going to 11.2, I don't know how to get into it. Even if the .619 version is there.
the way to 'access' a local iso is by 'loop mounting' it, as in: mount -o loop /path/to/name-of.iso /mnt/ But downgrading to the versions on the iso might bring a whole other set of complications, so if at all possible I would go for updating instead.
Keep in mind that I'm a fairly advanced _user_ with no more SA skills than one learns by watching and asking questions on this list (embedded systems engineer -- wasn't even sure what "systems administrator" meant until subscribing here :-).
you will definitely want to have a look at 'rpm --help' and 'man rpm' before and during the above... ;) hth /jon -- YMMV -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org