Bug 481427

Description of problem:
The release tag (ENVRA) of the pexpect RPM package in Red Hat Enterprise Linux 
4.7 needs to get bumped from -1 to -2 in order to obsolete the EPEL package 
correct.

The current pexpect RPM package in Red Hat Enterprise Linux was pilfered/
purloined (I got pointed, that "stealing" as I used before is the wrong word 
even if it says the same) from EPEL (Extra Packages for Enterprise Linux), 
where I am/was the long time package maintainer.

The situation is now, if you were using RHEL 4.5 or 4.6 with EPEL and you've 
e.g. installed the duplicity package, the pexpect-2.3-1.el4 package dropped in
from EPEL as dependency. With RHEL 4.7, Red Hat had then decided to put the
pexpect-2.3-1.el4 package into RHEL 4.7, but without any increasing of version
number (maybe it wasn't even rebuilt?).

As "pexpect-2.3-1.el4" from EPEL and "pexpect-2.3-1.el4" from RHEL 4.7 are now
exactly the same, the package never got replaced. So I'm now expecting RHEL
customers out there, that still use the unsupported EPEL package rather the
supported RHEL package. The only way to solve this is, that Red Hat bumps the
release tag from -1 to -2 and pushs an update out to the customer.

As unluckily the regular package maintainer on Red Hat side of pexpect never
showed up on my old bug report #452762 and that guy has shown no reaction to
e-mails in the past too, I'm trying hereby via some Fedora involved Red Hat 
people to get him a clout and maybe somebody of the Red Hat guys can put him 
into a RPM packaging training. Forgetting and/or ignoring such RPM basics when
scrounging a package should never happen.

Note, that I've absolutely no problem with pilfering/purloining/scrounging one
or multiple of my RPM packages, spec files etc., but then please do it correct 
- bump release, add %changelog and stuff...otherwise you shouldn't IMHO be a 
RPM package maintainer.

Version-Release number of selected component (if applicable):
pexpect-2.3-1.el4

How reproducible:
Everytime, see above.

Actual results:
pexpect-2.3-1.el4 from RHEL 4.7+ isn't able to obsolete the original and base
pexpect-2.3-1.el4 package from EPEL and the maintainer on Red Hat side takes
no action; the problem can't be solved by EPEL.

Expected results:
pexpect-2.3-2.el4 in RHEL which supersedes my original and base package from
EPEL.