Bug 2031808 - perl-Net-OpenID-Consumer for EPEL 9
Summary: perl-Net-OpenID-Consumer for EPEL 9
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: perl-Net-OpenID-Consumer
Version: epel9
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jitka Plesnikova
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 2032231
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-12-13 13:26 UTC by Xavier Bachelot
Modified: 2022-01-12 00:56 UTC (History)
2 users (show)

Fixed In Version: perl-Net-OpenID-Consumer-1.18-18.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-01-12 00:56:09 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Xavier Bachelot 2021-12-13 13:26:05 UTC 
Hi,

Could you please branch and build perl-Net-OpenID-Consumer for EPEL 9 ?

Regards,
Xavier
Comment 1 Jitka Plesnikova 2021-12-14 10:03:11 UTC 
https://pagure.io/releng/fedora-scm-requests/issue/39534
Comment 2 Jitka Plesnikova 2021-12-14 10:06:04 UTC 
(In reply to Jitka Plesnikova from comment #1)
> https://pagure.io/releng/fedora-scm-requests/issue/39534
Wrong link
https://pagure.io/releng/fedora-scm-requests/issue/39535
Comment 3 Fedora Update System 2022-01-03 15:11:47 UTC 
FEDORA-EPEL-2022-b88f39e70d has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-b88f39e70d
Comment 4 Fedora Update System 2022-01-04 00:27:20 UTC 
FEDORA-EPEL-2022-b88f39e70d 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-b88f39e70d

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 5 Fedora Update System 2022-01-12 00:56:09 UTC 
FEDORA-EPEL-2022-b88f39e70d 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.