DescriptionNathan G. Grennan
2004-10-30 18:59:53 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3)
Gecko/20041020 Galeon/1.3.17.99
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
doesn't.
Version-Release number of selected component (if applicable):
rpm-4.3.2-13
How reproducible:
Always
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
Additional info:
"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
previously-installed packages."
Comment 1Nathan G. Grennan
2004-10-30 19:06:17 UTC
I got Actual and Expected Results reversed.
This default change could also have negative security effects.
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)
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20041020 Galeon/1.3.17.99 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 doesn't. Version-Release number of selected component (if applicable): rpm-4.3.2-13 How reproducible: Always 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 Additional info: "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 previously-installed packages."