Bug 2033633 - Add perl-Types-Path-Tiny to EPEL 9
Summary: Add perl-Types-Path-Tiny to EPEL 9
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: perl-Types-Path-Tiny
Version: epel9
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Petr Pisar
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 2032430
Blocks: 2032431
TreeView+ depends on / blocked
 
Reported: 2021-12-17 13:55 UTC by Petr Pisar
Modified: 2022-02-05 01:35 UTC (History)
3 users (show)

Fixed In Version: perl-Types-Path-Tiny-0.006-13.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-02-05 01:35:56 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Petr Pisar 2021-12-17 13:55:44 UTC
I need perl-Types-Path-Tiny in EPEL 9 for perl-Types-URI. Could please add it there? If you are not interested in it make me (ppisar) an EPEL admin and I will take care about the package there.

Comment 1 Ralf Corsepius 2022-01-26 08:22:19 UTC
Petr, you already are "collaborator" and BZ-contact for EPEL.

Comment 2 Petr Pisar 2022-01-26 16:56:56 UTC
I did not noticed. Thanks for the hint.

https://pagure.io/releng/fedora-scm-requests/issue/41358

Comment 3 Fedora Update System 2022-01-26 17:23:28 UTC
FEDORA-EPEL-2022-8625cb0e0e has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-8625cb0e0e

Comment 4 Fedora Update System 2022-01-27 19:12:14 UTC
FEDORA-EPEL-2022-8625cb0e0e has been pushed to the Fedora EPEL 9 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-8625cb0e0e

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 5 Fedora Update System 2022-02-05 01:35:56 UTC
FEDORA-EPEL-2022-8625cb0e0e has been pushed to the Fedora EPEL 9 stable repository.
If problem still persists, 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.