Bug 50515 - Unexpected behavior if file would overrides directory
Summary: Unexpected behavior if file would overrides directory
Alias: None
Product: Red Hat Raw Hide
Classification: Retired
Component: rpm   
(Show other bugs)
Version: 1.0
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Jeff Johnson
QA Contact: David Lawrence
Depends On:
TreeView+ depends on / blocked
Reported: 2001-07-31 19:49 UTC by Enrico Scholz
Modified: 2007-04-18 16:35 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-07-31 19:51:59 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
sample spec-file for step (1) (293 bytes, text/plain)
2001-07-31 19:51 UTC, Enrico Scholz
no flags Details

Description Enrico Scholz 2001-07-31 19:49:19 UTC
Description of Problem:

When having an RPM containing a symlink or ordinary file having the same
name as an already existing directory, a file with a strange name will be
created without any message/warning.

The strange name may be ok (a suffix like .rpmnew would be perhaps better)
but a warning would be advisably in any case.

Steps to Reproduce:
1. build package containing file /tmp/XXX
2. mkdir /tmp/XXX
3. rpm -U <package>.rpm
4. ls -d /tmp/X*

Actual Results:

no message at (3)


Expected Results:

a warning

Additional Information:


Comment 1 Enrico Scholz 2001-07-31 19:51:55 UTC
Created attachment 25671 [details]
sample spec-file for step (1)

Comment 2 Jeff Johnson 2001-07-31 19:57:25 UTC
This is a packaging problem. rpm does not permit (and never has)
replacing a directory on disk with a symlink from the package.
You need to fix what ever package is trying to do this.

Meanwhile the strange name is a semi-colon followed by the
install time in seconds. New to rpm-4.0.3 is installing with a
temp name (i.e. the name followed by the semi-colon and time),
and then renaming into place.

Comment 3 Enrico Scholz 2001-07-31 20:28:27 UTC
How can I determine if a package has such a problem and which files are being

Have I to wait for bugreports of users who don't know why they have such files? 

A warning at installation-time would be highly appropriate.

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