Bug 1755810 - [RFE] EPEL8 branch of perl-DateTime-Format-SQLite
Summary: [RFE] EPEL8 branch of perl-DateTime-Format-SQLite
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: perl-DateTime-Format-SQLite
Version: epel8
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jitka Plesnikova
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-09-26 09:21 UTC by Gary Buhrmaster
Modified: 2019-10-12 01:50 UTC (History)
5 users (show)

Fixed In Version: perl-DateTime-Format-SQLite-0.11-28.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-12 01:50:13 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Gary Buhrmaster 2019-09-26 09:21:06 UTC
Description of problem:

Please provide the perl-DateTime-Format-SQLite package for EPEL8.

Comment 2 Fedora Update System 2019-09-26 15:20:58 UTC
FEDORA-EPEL-2019-2e8e01536a has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-2e8e01536a

Comment 3 Fedora Update System 2019-09-27 02:36:55 UTC
perl-DateTime-Format-SQLite-0.11-28.el8 has been pushed to the Fedora EPEL 8 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-2e8e01536a

Comment 4 Gary Buhrmaster 2019-09-27 19:53:40 UTC
Depends On: #1756512

Comment 5 Gary Buhrmaster 2019-09-27 19:57:25 UTC
My bad, the perl-DateTime-Format-Builder package is in the additional repo I forgot to enable.

Comment 6 Fedora Update System 2019-10-12 01:50:13 UTC
perl-DateTime-Format-SQLite-0.11-28.el8 has been pushed to the Fedora EPEL 8 stable repository. If problems still persist, please make note of it in this bug report.


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