Bug 32357 - new rpm-4.0.2 causes up2date/gnorpm to fail
Summary: new rpm-4.0.2 causes up2date/gnorpm to fail
Status: CLOSED DUPLICATE of bug 32301
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: rpm
Version: 6.2
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Jeff Johnson
QA Contact: David Lawrence
Depends On:
TreeView+ depends on / blocked
Reported: 2001-03-20 02:58 UTC by Need Real Name
Modified: 2007-04-18 16:32 UTC (History)
0 users

Clone Of:
Last Closed: 2001-03-20 02:59:03 UTC

Attachments (Terms of Use)

Description Need Real Name 2001-03-20 02:58:54 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.72 [en] (X11; U; Linux 2.4.1 i686)

I used up2date to download and install the new version of rpm as
suggested.  The installer correctly downloaded and installed the rpms for
rpm.  When I run rpm or gnorpm again, I get the error:
Traceback (innermost last):
  File "/usr/sbin/up2date", line 9, in ?
    import rpm
ImportError: /usr/lib/librpm.so.0: undefined symbol: fdio
I was able to run rpm --rebuild as suggested on the 6.2 bug fix page for
the new rpm package but rpm still does not work.

Reproducible: Always
Steps to Reproduce:
1. Upgrade a 6.2 box to the new rpm
2. Try to run gnorpm or up2date
3. Get an error...

Actual Results:  trying to run up2date I get:
Traceback (innermost last):
  File "/usr/sbin/up2date", line 9, in ?
    import rpm
ImportError: /usr/lib/librpm.so.0: undefined symbol: fdio

trying to run gnorpm I get:
gnorpm: error in loading shared libraries: /usr/lib/librpm.so.0: undefined
symbol: fdio

Expected Results:  Instead of getting an error the two applications up2date
and gnorpm should have started normally.

I feel that this is a bug since I downloaded the new rpm's directly from
the RedHat website and up2date and gnorpm now cease to work.  I assume it
is some sort of library dependency that wasn't taken into account.

Comment 1 Bill Nottingham 2001-03-20 03:04:22 UTC

*** This bug has been marked as a duplicate of 32301 ***

Note You need to log in before you can comment on or make changes to this bug.