Bug 2065710 - libjoedog: please provide epel9 package
Summary: libjoedog: please provide epel9 package
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: libjoedog
Version: epel9
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Denis Fateyev
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-03-18 14:44 UTC by Denis Fateyev
Modified: 2022-04-14 17:08 UTC (History)
3 users (show)

Fixed In Version: libjoedog-0.1.2-18.el9
Clone Of:
Environment:
Last Closed: 2022-04-14 17:08:54 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Denis Fateyev 2022-03-18 14:44:33 UTC 
Description of problem:
Please provide "libjoedog" package in EPEL9
Comment 1 Denis Fateyev 2022-03-26 13:41:47 UTC 
Please request "libjoedog" epel9 branch — only package's epel maintainers can perform it.
Alternatively, you could add me as a package maintainer, so I could request the branch and push the update from my side.
Comment 2 Denis Fateyev 2022-04-06 17:01:59 UTC 
Stalled EPEL package libjoedog:
https://pagure.io/releng/issue/10739

EPEL9 branch request:
https://pagure.io/releng/fedora-scm-requests/issue/43515
Comment 3 Fedora Update System 2022-04-06 17:11:22 UTC 
FEDORA-EPEL-2022-ab549eafe4 has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-ab549eafe4
Comment 4 Fedora Update System 2022-04-06 19:44:58 UTC 
FEDORA-EPEL-2022-ab549eafe4 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-ab549eafe4

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 5 Fedora Update System 2022-04-14 17:08:54 UTC 
FEDORA-EPEL-2022-ab549eafe4 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.