Bug 136456 - '--oldpackage' will remove library symlinks
Summary: '--oldpackage' will remove library symlinks
Status: CLOSED DUPLICATE of bug 139233
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: rpm (Show other bugs)
(Show other bugs)
Version: 3.0
Hardware: x86_64 Linux
Target Milestone: ---
Assignee: Jeff Johnson
QA Contact: Mike McLean
Depends On:
TreeView+ depends on / blocked
Reported: 2004-10-20 07:33 UTC by Jay Turner
Modified: 2015-01-08 00:08 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-02-21 19:06:29 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Jay Turner 2004-10-20 07:33:39 UTC
Description of problem:
Seeing this with rpm-4.2.3-10 on an x86_64 when dealing with multi-lib
packages, but almost looks like we would see the same behavior no
matter the platform or if we were dealing with multi-lib.

Anyway, have a machine with the following:

I then decide to go back to the old packages, so I run
rpm -vv -Uh --oldpackage libtiff*rpm

Which attempts to reinstall the libtiff-3.5.7-13 packages.  After
completion of this task, I'm missing both /usr/lib/libtiff.so.3 and

Poking through the verbose rpm output, I see that the old packages get
installed first, running ldconfig after each installation (so the
links get created) then we start removing the -20.1 packages and I get
output like this for both the i386 and x86_64 packages:

D: fini      100755  1 (   0,   0)    264132 /usr/lib/libtiff.so.3.5 skip
D: fini      120777  1 (   0,   0)        14 /usr/lib/libtiff.so.3 

(of course, substituting lib64 for the x86_64 case)  Net result, don't
remove the libtiff.so.3.5 file, as it's owned by the freshly installed
package, but do remove the libtiff.so.3 symlink, as it's not owned by
anything.  This would be all swell and dandy if we just reran ldconfig
after the package removal, instead it appears that "rpm knows best":

erase: %postun(libtiff-3.5.7-20.1) skipping redundant "/sbin/ldconfig".

So we're left with a system without /usr/lib/libtiff.so.3 and

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
Actual results:

Expected results:

Additional info:

Comment 1 Jeff Johnson 2004-10-20 14:59:54 UTC
The option --oldpackage (and --force) has never been supported by
Red Hat or rpm afaik.

Anyways, there's a 2 line fix available to turn off skipping
ldconfig on downgrade. The same issue seen when elfutils
was released as downgrade around the 1st of the year, another
"feature" that Red Hat and rpm have never ever supported.

Comment 3 Jeff Johnson 2004-11-14 22:05:47 UTC

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

Comment 4 Red Hat Bugzilla 2006-02-21 19:06:29 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

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