From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3)
Description of problem:
Two installed packages own the files in the same directories largely
defeats the point of package management. It is likely to cause broken
applications in many cases. Say two Gnome packages use the same
library, but want to compiled with different options. So that their
own versions of the file are mutally exclusive. So package A was
installed and working. Package B is installed and overwrites
/usr/lib/libgnomefoo.so.1. Now application B works and application A
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. rpm -i packagea.rpm
2. rpm -i packageb.rpm
Actual Results: File conflicts by default
Expected Results: No file conflicts by default
"RPM's default behavior regarding file conflicts in Fedora Core 3 has
changed. In the past, file conflicts (where a file from one
already-installed package also appears in a package that is to be
installed) caused the installation of the package containing the
conflicting file to abort.
In Fedora Core 3, RPM will ignore such conflicts, and the package
installation will proceed, overwriting any conflicting files from
I got Actual and Expected Results reversed.
This default change could also have negative security effects.
File conflicts reenabled by default in rpm-4.3.2-18.
REOPEN because it was not built in dist-fc3-HEAD, but rather dist-fc4.
rel-eng will need to accept this in order for this bug to be closed.
*** Bug 131766 has been marked as a duplicate of this bug. ***
Copy Warren :)
Fix summary to show better in the dependency list for the FC3Blocker.
Warren, please be careful when closing bugs as duplicate (you should
have closed this bug as duplicate and left #131766 alone, since that
was the older one filed)
I'm glad this change was reverted.