On 2/4/06, Jim Cornette <fct-cornette@xxxxxxxxxxxxxx> wrote: > Jonathan Berry wrote: > > I'm seeing a similar thing on my x86_64 box: > > # rpm -qa | grep glibc | sort > > glibc-2.3.90-30.i686 > > glibc-2.3.90-30.x86_64 > > glibc-2.3.90-34.i686 > > glibc-2.3.90-34.x86_64 > > glibc-common-2.3.90-30.x86_64 > > glibc-common-2.3.90-34.x86_64 > > glibc-devel-2.3.90-30.i386 > > glibc-devel-2.3.90-30.x86_64 > > glibc-devel-2.3.90-34.i386 > > glibc-devel-2.3.90-34.x86_64 > > glibc-headers-2.3.90-30.x86_64 > > glibc-headers-2.3.90-34.x86_64 > > glibc-kernheaders-3.0-4.x86_64 > > > > I have both versions for both architectures, heh. The update that > > pulled in the 2.3.90-34 versions went rather rough. I had to > > constantly go kill off gcj-dbtool because otherwise yum would just sit > > there. I guess there is no telling what might be broken as a result > > of that... > > > > Jonathan > > The newest glibc update must have cleaned all of this up as I no longer have multiple versions (only multiple arch as I should :)). $ rpm -qa | grep glibc glibc-2.3.90-35.i686 glibc-common-2.3.90-35.x86_64 glibc-devel-2.3.90-35.i386 glibc-2.3.90-35.x86_64 glibc-headers-2.3.90-35.x86_64 glibc-kernheaders-3.0-4.x86_64 glibc-devel-2.3.90-35.x86_64 > So was a bug report made regarding gcj-dbtool? I do not have this > program installed and did not suffer the wrath from the package lockup. See https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=179228 Seems to be another symptom of the same bug. > Killing yum in process during the installation phase will result in no > cleanup after install. Probably packages downloaded to upgrade and were Actually, it is not yum that I killed, it was gcj-dbtool itself. It seems to get run after updating packages that have to do with java, so it was running and causing yum to hang. Killing it allows yum to go on, but obviously doesn't do all that it was supposed to for that package. > not upgraded because of the kill were never installed. Packages before > gcj-dbtool probably only have multiple version entries in the rpmdb and gcj-dbtool wasn't being upgraded, but rather was being used in one of the install scriptlets for doing some java stuff. > are probably only entries for the earlier program on your system and the > database entries for the older version need only to be erased. Verifying > the later packages is still a good idea to ensure that all of the new > packages are intact. Jonathan -- fedora-test-list mailing list fedora-test-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list