On Fri, 23 Sep 2011 11:57:31 +0200, CA (Christoph) wrote: > >> Try to erase the -2 version of glibc.x86_64: > >> rpm --justdb -e --noscripts glibc-2.13-2.x86_64 > > > > rpm --justdb -e --noscripts glibc-2.13-2.x86_64 > > error: Failed dependencies: > > glibc = 2.13-2 is needed by (installed) glibc-common-2.13-2.x86_64 > > glibc = 2.13-2 is needed by (installed) glibc-headers-2.13-2.x86_64 > > glibc = 2.13-2 is needed by (installed) glibc-devel-2.13-2.x86_64 > > > > > > rpm --justdb -e --noscripts glibc-2.13-1.x86_64 > > rpm -qa glibc > glibc-2.13-1.i686 > glibc-2.13-2.x86_64 Oh no, you've messed up your installation further. ;) Erasing the _older_ glibc made no sense, since you want to update from the older i686/x86_64 pair of packages to the newer glibc builds. Instead, you should have added the -2 builds of glibc-common, glibc-headers and glibc-devel to the --justdb erase command. Now it has become much harder to help. What I would try now is to erase also the -1 glibc i686 packages (again with --justdb ...) and also any glibc-* subpackages for i686 which are still installed (rpm -qa glibc\*). Then "yum install glibc.i686" which should pull in the -2 build matching your installed -2 x86_64 pkg. You are on x86_64, so temporarily erasing the i686 pkg from the RPM database is much more harmless than playing with x86_64 pkgs. -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
