From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.5 (X11; Linux i686; U;) Gecko/20020713
Description of problem:
The following package in the url is the package. If you go to the jpackage.org
site and examine the spec file you will notice they have two packages.
ant-optional and ant-optional-full. The ant-optional-full contains the same
libraries as ant-optional full, different filenames, but the full has more
compiled into it.
Since jpackage is providing the same package as ant-optional in there rpm
namespace with ant-optional-full they put the provides: ant-optional tag. Make
sense. Now you don't want to have them both install at the same time so they
put in a Conflicts: ant-optional. When you go to do an install you get the
[pearcec@mp3 a]$ sudo rpm -Uvh ant-optional-full-1.5-4jpp.noarch.rpm
error: failed dependencies:
ant-optional conflicts with ant-optional-full-1.5-4jpp
rpm should smart enough to allow this during the install. Some flag in the
code. If the package installing provides and conflicts the same package it
should allow it to install.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
The description above should be enough to understan the problem.
Yup, that's the way conflicts is supposed to work.
Some means other than "smarter rpm" and Conflicts: is needed to
package the minimal -> full upgrade path as described.
In fact, I suspect that adding Obsoletes: to each package
to eliminate the other is closer to the desired behavior.