Bug 35899 - rpm 4.0.2-6x breaks kpackage
rpm 4.0.2-6x breaks kpackage
Status: CLOSED WORKSFORME
Product: Red Hat Linux
Classification: Retired
Component: rpm (Show other bugs)
6.2
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Jeff Johnson
David Lawrence
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2001-04-13 14:52 EDT by John McHarry
Modified: 2007-04-18 12:32 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2001-04-17 12:14:13 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description John McHarry 2001-04-13 14:52:48 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows 98)


After upgrading to rpm 4.0.2-6x kpackage no longer works.  Clicking on it 
appears to do nothing.

Reproducible: Always
Steps to Reproduce:
1. upgrade to rpm 4.0.2-6x
2. start kde
3. click on kpackage or click on an rpm file in the viewer

	

Actual Results:  nothing

Expected Results:  should have opened kpackage either showing what is 
installed, or showing the rpm selected

This seems consistent across a few machines.  Also, gnorpm no longer seems 
to work.
Comment 1 Gene Willacker 2001-04-17 12:14:10 EDT
When logging out of X, my console has the following text on it, after the 
normal X startup messages:

"kpackage: error in loading shared libraries: /usr/lib/librpmbuild.so.0: 
undefined symbol: rpmGlobalMacroContext"
Comment 2 Jeff Johnson 2001-07-29 12:14:39 EDT
Rebuilding kpackage will fix your problem. The more general
fix, getting a solid ABI into rpmlib so that an upgrade of rpm
doesn't break existing executables is underway, but is gonna
take a while to deploy to Red Hat 6x platforms.

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