Bug 847128 - epel6 build request
Summary: epel6 build request
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: perl-DateTime-Format-Oracle
Version: 19
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
Assignee: Petr Šabata
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 847299
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-08-09 19:29 UTC by Bill Pemberton
Modified: 2014-09-10 15:25 UTC (History)
3 users (show)

Fixed In Version: perl-DateTime-Format-Oracle-0.06-3.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-09-10 15:25:50 UTC


Attachments (Terms of Use)

Description Bill Pemberton 2012-08-09 19:29:37 UTC
Please build perl-DateTime-Format-Oracle for epel6.

Comment 1 Petr Šabata 2012-08-10 13:29:18 UTC
This will require getting perl(Convert::NLS_DATE_FORMAT) into EPEL6 first...

Comment 2 Bill Pemberton 2012-08-10 13:40:44 UTC
Ok, thanks.  I've put in a request for perl(Convert::NLS_DATE_FORMAT)

Comment 3 Bill Pemberton 2013-01-07 18:29:42 UTC
A little bump for this.  perl(Convert::NLS_DATE_FORMAT) is in EPEL6 now.

Comment 4 Fedora End Of Life 2013-04-03 19:40:58 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.

(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19

Comment 5 Fedora Update System 2013-04-29 14:16:07 UTC
perl-DateTime-Format-Oracle-0.06-3.el6 has been submitted as an update for Fedora EPEL 6.
https://admin.fedoraproject.org/updates/perl-DateTime-Format-Oracle-0.06-3.el6

Comment 6 Fedora Update System 2013-05-14 17:46:21 UTC
perl-DateTime-Format-Oracle-0.06-3.el6 has been pushed to the Fedora EPEL 6 stable repository.


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