Bug 249841 - EPEL branches for perl-Devel-Symdump and perl-TermReadKey
Summary: EPEL branches for perl-Devel-Symdump and perl-TermReadKey
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: perl-Devel-Symdump
Version: 8
Hardware: All
OS: Linux
medium
low
Target Milestone: ---
Assignee: Robin Norwood
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: bzcl34nup
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-07-27 13:03 UTC by Robin Norwood
Modified: 2008-07-05 09:19 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-07-05 09:19:27 UTC
Type: ---
Embargoed:
wtogami: fedora-cvs+


Attachments (Terms of Use)

Description Robin Norwood 2007-07-27 13:03:54 UTC
These two packages need EPEL branched to satisfy deps

Package Change Request
======================
Package Name: perl-Devel-Symdump
New Branches: EL-4 EL-5


Package Change Request
======================
Package Name: perl-TermReadKey
New Branches: EL-4 EL-5

Comment 1 Bug Zapper 2008-04-04 13:27:30 UTC
Based on the date this bug was created, it appears to have been reported
during the development of Fedora 8. In order to refocus our efforts as
a project we are changing the version of this bug to '8'.

If this bug still exists in rawhide, please change the version back to
rawhide.
(If you're unable to change the bug's version, add a comment to the bug
and someone will change it for you.)

Thanks for your help and we apologize for the interruption.

The process we're following is outlined here:
http://fedoraproject.org/wiki/BugZappers/F9CleanUp

We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.

Comment 2 Johan Kok 2008-07-05 09:19:27 UTC
This issue seems resolved, but still has status NEW. There are perl-Devel-Sysdump and perl-
TermReadKey packages in both the EPEL-4 and EPEL-5 repository. I'm closing this issue, sorry for the 
Bugzilla noise. 


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