Description of problem:

While studying the primary.xml of RHEL 5 RHN repositories i stumbled across a
wrong entry in the file for specific cases:

If a package had a

  Requires: foo-1.2.3

the entry in the primary.xml would look like this:

 <rpm:entry name="foo" flags="EQ" epoch="0" ver="1.2.3" rel="0" />

instead of 

 <rpm:entry name="foo" flags="EQ" epoch="0" ver="1.2.3" />

FC6 and FC7 repositories don't contain the rel="0" entries for such cases. I've
verified this for a few cases, the first one i found was guile-devel requiring
guile.

Version-Release number of selected component (if applicable):

RHEL 5 Client installation.

yum-rhn-plugin-0.4.3-1.el5
rhnsd-4.6.1-1.el5
rhnlib-2.2.5-1.el5
rhn-check-0.4.13-1.el5
rhn-setup-gnome-0.4.13-1.el5
rhn-client-tools-0.4.13-1.el5
rhn-setup-0.4.13-1.el5

How reproducible:

Always

Steps to Reproduce:
1. Install a RHEL 5
2. Run yum update to generate the local caches
3. Look for guile-devel in primary.xml and compare it to a FC6 primary.xml
4. Check the real package require of guile-devel
  
Actual results:

primary.xml contains requirements that contain additional wrong information.

Expected results:

primary.xml should contain the actual information as stored in the binary rpm.

Additional info:

This is luckly currently not an issue for RHEL 5, but in case yum ever gets
updated to 3.1.x or newer this will break as yum then uses the information from
the repodata (primary.xml) instead of binary headers as in yum-3.0.x and
earlier. Also for RHEL 6 we will be including a newer yum, so there it
definitely will break otherwise.

Suggested fix is to use a normal createrepo which doesn't show this artefact in
primary.xml (recreated the primary.xml myself and it didn't contain the rel="0"
entries).

Read ya, Phil