Bug 79077 - rpm creates broken symlinks
rpm creates broken symlinks
Product: Red Hat Linux
Classification: Retired
Component: rpm (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jeff Johnson
Depends On:
  Show dependency treegraph
Reported: 2002-12-05 08:18 EST by Juho Schultz
Modified: 2008-05-01 11:38 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2002-12-05 08:18:34 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Juho Schultz 2002-12-05 08:18:27 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003

Description of problem:
rpm -Uvh creates also broken symlinks when the package suggests so.
No warning or notice is given to the user.

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

How reproducible:

Steps to Reproduce:
1. Obtain a rpm that creates broken symlinks.
(e.g. nmap-frontend-3.00-1.i386.rpm from
2. rpm -Uvh nmap-frontend-3.00-1.i386.rpm

Actual Results:  The following files are created:
/usr/bin/xnmap -> /usr/bin/nmapfe
/bin/xnmap -> /bin/nmapfe
The last one is a broken link.

Expected Results:  rpm should check for creating broken links. At minimum a
warning 'created a link to non-existing file' should be given, or preferably
'trying to create link to non-existing file. Proceed?'

Additional info:

The problem has also been reported to the
maintainer of the nmap-frontend package.
Comment 1 Jeff Johnson 2002-12-06 12:09:32 EST
This is a package, not rpm, problem. The problem
is more complicated than stat'ing the target, as
there are implicit ordering constraints (and
painful loops) on installed packages that would be
needed as well (read: 2nd package may install target that
1st package symlinks too).

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