Description of problem:
rpm-4.3-0.21 references glib 2.3.4 but FC2 test1 is using glib-2.3.3
This causes problems w/ up2date (librpmio complains that GLIB_2.3.4 is
undefined and terminates up2date). Was the development system using
glib-2.3.4? If so, it's outta sync w/ the rest of the rpms in
Version-Release number of selected component (if applicable):
rpm-*-4.3-0.21 from the ./development dir
Steps to Reproduce:
1. Upgraded FC1 to FC2 test
2. Installed rpm-4.3-0.21 from ./development dir
up2date, rpm busted
that rpm and up2date should function normally
workaround was to build rpm-*-4.3-0.21.i386.rpm from SRPM files and
install using: rpm -iUvh --force
other workaround would have been to upgrade glibc to 2.3.4
Installing new glibc from devel tree should get around this.
Thanks. I think that's what I was suggesting too. The problem is that
the glibc RPM packages in the devel tree seem to be sitting at
2.3.3-17, not 2.3.4, unless I'm interpreting the numbering wrong.
Thus it's quite easy for folks to "break" librpmio w/o realizing.
glibc-2.3.3-17.i386.rpm 17-Mar-2004 14:40 3.3M
This is a weak symbol in glibc-2.3.3 against which rpm