pexepct is in RHEL and should be dropped from EPEL

David Juran djuran at redhat.com
Thu Jan 22 16:23:32 UTC 2009


On Thu, 2009-01-22 at 10:41 +0100, Robert Scheck wrote:

> How do you expect that we perform the dropping? We can't remove branches
> that already exist - spoken for CVS. And the pexpect package *has* to
> remain in EPEL for users that did not upgrade to RHEL 5.2 (5.0.x, 5.1.x);
> otherwise e.g. duplicity will get immediately unusable on such systems.

Since the version of the packages really is the same in both EPEL and
RHEL (pyexpect-2.3-1) I guess the proper thing to do would be to bump
the release number in RHEL. Or possibly the other way around, by
downgrading the EPEL versions to  
pyexpect-2.3-0.5...

-- 
David Juran
Sr. Consultant
Red Hat
+358-504-146348
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
URL: <http://lists.fedoraproject.org/pipermail/epel-devel/attachments/20090122/643f166e/attachment.sig>


More information about the epel-devel mailing list