From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040113 Description of problem: When attempting to run up2date, I get an error message: Traceback (most recent call last): File "/usr/sbin/up2date", line 12, in ? import rpm ImportError: /usr/lib/librpmio-4.3.so: symbol regexec, version GLIBC_2.3.4 not defined in file libc.so.6 with link time reference GLIBC_2.3.4 is not available and rpm-4.3-0.19 is not available either. Version-Release number of selected component (if applicable): up2date-4.3.11-2.1.1, rpm-4.3-0.20, glibc-2.3.3-13 How reproducible: Always Steps to Reproduce: 1. run up2date 2. 3. Actual Results: Traceback (most recent call last): File "/usr/sbin/up2date", line 12, in ? import rpm ImportError: /usr/lib/librpmio-4.3.so: symbol regexec, version GLIBC_2.3.4 not defined in file libc.so.6 with link time reference Expected Results: Ability to up2date properly Additional info: To save on downloading problems with versioning of various packages, I usually start with a letter and update them, for example, just the r*rpm packages. I let up2date pick the dependencies if there are any and don't get the packages that don't seem to have matching dependencies. At the time I had updated on 3/13/04 from z back to r.
This bug has broken yum as well.
What does "rpm -V --nofiles rpm rpm-python" say when you reach the state above?
I do not get any output from that command, just back to the prompt, whether root or a user. Do you want a package listing? glibc-2.3.3-13 glibc-common-2.3.3-13 glibc-debug-2.3.3-13 glibc-devel-2.3.3-13 glibc-headers-2.3.3-13 glibc-kernheaders-2.4-8.43 glibc-profile-2.3.3-13 glibc-utils-2.3.3-13 python-2.3.3-2 python-devel-2.3.3-2 python-docs-2.3.3-2 python-optik-1.4.1-5 python-tools-2.3.3-2 rpm-4.3-0.20 rpm-build-4.3-0.20 rpmdb-fedora-1.90-0.20040312 rpm-devel-4.3-0.20 rpm-python-4.3-0.20
This dependency chain should have associated the needed glibc symbol with librpmio used by rpm-python: $ rpm -q --requires rpm-python | grep rpmio librpmio-4.3.so $ rpm -q --provides rpm | grep rpmio librpmio-4.3.so $ rpm -q --requires rpm | grep 2.3.4 libc.so.6(GLIBC_2.3.4) $ rpm -q --provides glibc | grep 2.3.4 libc.so.6(GLIBC_2.3.4) Somehow rpm was updated w/o glibc being updated. The "rpm -V --nofiles rpm rpm-python" command verified that that dependency chain was actually in place. I suspect that your up2date is functioning now. Is that the case?
Ran those 4 commands and got those responses but up2date does not work yet.
Off to up2date for diagnosis then. All I can thinkof is that up2date is using a different rpmmodule.so somehow. You might want do do rpm -V rpm rpm-python glibc to insure that all the files are as expected.
As far as I can tell, rpm is working fine. I can update, install and remove from the command line. Did not get any output from the above command though.
Updated to the latest rpm and glibc and the problem is fixed. Thanks.