Hi All, While updating glibc-2.2-7.i386 to glibc-2.2-25.i386 the next err is seen: It conflicts with ldso-1.9.9-72 However such a file canot be found on system, neither yast nor find gets such a file. Rpm -i --nodeps also stops while updating. Any hints? Thanks Antal ++++++++++++++++++++ Kreorg Oktatóközpont Hunyadi tér 8, Budapest 1067 ++++++++++++++++++++ kreorg@kreorg.hu http://www.kreorg.hu ++++++++++++++++++++ Grid - Erő a változáshoz.
Hi All,
While updating glibc-2.2-7.i386 to glibc-2.2-25.i386 the next err is seen:
It conflicts with ldso-1.9.9-72
However such a file canot be found on system, neither yast nor find gets such a file. Rpm -i --nodeps also stops while updating.
Any hints?
This seems to be a non-SuSE system, at least there was. You can try to remove the ldso package - there is no such package in a SuSE system. According to the glibc version, you have a SuSE Linux 7.1 system. In that system, there is a file called /lib/ld.so.1.9.9, it belongs to the shlibs5 package (the old libc5 shared libraries). Now this is what I would do: 1) check which ld.so files there exist in the system: ls -la /lib/ld* If there is a /lib/ld-2.2.so and a /lib/ld-linux.so.2, you are safe. These two files (one is a link) are present, you are safe. They must not be removed. 2) If there is a /lib/ld.so.1.9.9, check which package it belongs to: rpm -qf /lib/ld.so.1.9.9 If the package name is ldso, then check its details in the rpm db: rpm -qi ldso. You should be able to remove it: rpm -e ldso If the file belongs to shlibs5, then remove the shlibs5 package. Theoretically, not a single package should depend on shlibs5, maybe with the exception of some emulator.
Thanks Antal
Happy new year! Roman.
* Roman Drahtmueller wrote on Mon, Jan 06, 2003 at 03:02 +0100:
It conflicts with ldso-1.9.9-72
This seems to be a non-SuSE system, at least there was. You can try to remove the ldso package - there is no such package in a SuSE system.
Without ld.so, you have to expect that nothing can be exec'd (started) in worsest case.
rpm -qf /lib/ld.so.1.9.9
If the package name is ldso, then check its details in the rpm db: rpm -qi ldso. You should be able to remove it: rpm -e ldso
Well, rpm works without ld.so, correct :) But please make sure you have at least one "sash" (stand alone shell) open in an independent terminal. I would suggest to copy the files that are part of the RPM before uninstalling it (I guess you don't have the RPM ld.so.rpm to reinstall on errors). When after rpm -e commands like "date" refuse to work, you have a backup. With sash, you can copy it back (since sash has a lot of tools build-in, remember "help" as special build-in command :)). oki, Steffen -- Dieses Schreiben wurde maschinell erstellt, es trägt daher weder Unterschrift noch Siegel.
Hi Steffen, Thanks for the comment. Let me ask, did you see my feedback to Roman's email? Sent to the list, too. There are the steps I made, and the results. It looked as if all went off well.
When after rpm -e commands like "date" refuse to work, you have a backup.
I tried it as user, : # > rpm -e date failed to open /var/lib/rpm/packages.rpm: Permission denied # > date Tue Jan 7 08:24:17 /etc/localtime 2003 Should I try it as root? It looks as if all went off well with the Glibc update. Please let me know if you think I missed something. Antal
* webmaster wrote on Tue, Jan 07, 2003 at 09:42 +0100:
I tried it as user, : # > rpm -e date failed to open /var/lib/rpm/packages.rpm: Permission denied
Should I try it as root?
No, don't do that! (Do not *try* anything when using linux.) Just for the case someone crawls the archives. Since it's OT the rest by PM. oki, Steffen -- Dieses Schreiben wurde maschinell erstellt, es trägt daher weder Unterschrift noch Siegel.
participants (3)
-
Roman Drahtmueller
-
Steffen Dettmer
-
webmaster