Bug 234233

Description of problem:
The upstream Sun JDK rpm has a virtual unversioned provides on xml-commons-apis.
We also have our own package called xml-commons-apis.
Due to certain rpm behaviors, these packages are incompatible.

When our xml-commons-apis package is updated, every other package that provides
xml-commons-apis will be removed (this includes the Sun JDK rpm). This means we
cannot have a package named xml-commons-apis. See
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=233713

The Sun JDK rpm also unversions its virtual provides of xml-commons-apis. This
means that no package can obsolete xml-commons-apis without removing the Sun
JDK. See https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=229791

So we are stuck in a situation in which we need to rename the xml-commons-apis
package without obsoleting xml-commons-apis. But renaming a package requires
obsoleting the old naming to provide a smooth update path. 


Version-Release number of selected component (if applicable):
Any version of package xml-commons-apis

How reproducible:
Always

Steps to Reproduce:
1. Install the Sun JDK
2. Install the xml-commons-apis package
3. Update the xml-commons-apis package
  
Actual results:
The Sun JDK rpm is removed from the system

Expected results:
The xml-commons-apis package should not remove the JDK package

Additional info:
This will also affect any of the products using xml-commons-apis in RHEL4