Bug 452762 - Just looking for the guy silently stole my EPEL 5 package
Just looking for the guy silently stole my EPEL 5 package
Status: CLOSED DUPLICATE of bug 481380
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: pexpect (Show other bugs)
All Linux
low Severity medium
: rc
: ---
Assigned To: Marek Grac
Depends On:
  Show dependency treegraph
Reported: 2008-06-24 17:09 EDT by Robert Scheck
Modified: 2016-04-26 10:14 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-08-20 09:09:04 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Robert Scheck 2008-06-24 17:09:06 EDT
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):

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.
Comment 1 Robert Scheck 2009-01-23 15:32:55 EST
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.
Comment 2 Marek Grac 2009-07-20 09:29:01 EDT

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.
Comment 3 Marek Grac 2009-07-30 04:29:56 EDT
* It looks like your package have to be removed from EPEL
* I will rebuild packages with new release number to fix current problems
Comment 4 Marek Grac 2009-08-20 09:09:04 EDT

*** This bug has been marked as a duplicate of bug 481380 ***

Note You need to log in before you can comment on or make changes to this bug.