From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/20020513
Description of problem:
Testing for conflicts during RPM install does not behave as expected if conflict
is with a particular version of itself.
It seems that the install checks are inspecting the version trying to install as
well as the RPM database to determine conflicts.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. rpm -i foo-2.1.0-8.i386.rpm
2. (spec file for foo contains "Conflicts: foo < 2.5.0-0")
3. rpm -Uvv foo-2.5.1-0.i386.rpm
Actual Results: foo successfully upgraded
Expected Results: foo should NOT have upgraded since existing foo was <
2.5.0-0; it should have spouted an error with failed dependencies because of
Here's my system specs:
[pauln@enki SPECS]$ sudo rpm --test -ivh ../RPMS/foo-2.5.1-1.i386.rpm
error: Failed dependencies:
foo < 2.5.0-0 conflicts with foo-2.5.1-1.i386
[pauln@enki SPECS]$ sudo rpm --test -Uvh ../RPMS/foo-2.5.1-1.i386.rpm
I don't think this is a bug, as upgrade implies erase/install so the final
system has no conflicting packages and the transaction is satisfied.