Description of problem: I'm using this bug report just to get the non-nice guy from Red Hat, who silently stole my nice pretty EPEL 5 package in order to put it into Red Hat Enterprise Linux 5.2...or am I seeing this completely wrong and I can cause RHBA and RHSA once I update pexpect in EPEL via EPEL CVS?! I guess, I can't, but let's see who is the "Assign To" once hitting "Commit". Version-Release number of selected component (if applicable): pexpect-2.3-1 How reproducible: Everytime since RHEL 5.2 Additional info: BTW, can I get please auto-CCed for each bug report somebody files against my former pexpect package on RHEL 5? I am still maintaining pexpect on all other branches. Thank you.
Replace "stole" by pilfered/purloined/scrounged when reading (I got pointed, that "stealing" as I used before is the wrong word even if it says the same). See also bug #481380 for further information, I've no problem that my package made it into RHEL and that I'm no longer owning it. But how the going-on was handled and which mistakes have been made there, is just a no-go.
Hi, I'm new maintainer of this package. It was 'stolen' because of me as I started to use pexpect in fencing agents (package cman/fence-agents). RHEL packages can't depend on EPEL packages. I'll try to fix those bugs this week.
* It looks like your package have to be removed from EPEL * I will rebuild packages with new release number to fix current problems
*** This bug has been marked as a duplicate of bug 481380 ***