Bug 2063968 - Please provide jdom for EPEL-9
Summary: Please provide jdom for EPEL-9
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: jdom
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Stefan Bluhm
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-03-14 18:34 UTC by Stefan Bluhm
Modified: 2022-03-25 21:26 UTC (History)
3 users (show)

Fixed In Version: jdom-1.1.3-30.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-03-25 21:26:52 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Stefan Bluhm 2022-03-14 18:34:59 UTC 
Hello,

can you please provide jdom for EPEL-9?

Thank you very much!
Comment 1 Mat Booth 2022-03-17 09:16:51 UTC 
Hi, no I'm not interested in maintaining EPEL branches. Do you want to be a co-maintainer so you can request your own EPEL branches?
Comment 2 Stefan Bluhm 2022-03-17 09:42:33 UTC 
Thank you Mat, I am up for that. Can you please add sbluhm?
Comment 3 Mat Booth 2022-03-18 15:19:38 UTC 
(In reply to Stefan Bluhm from comment #2)
> Thank you Mat, I am up for that. Can you please add sbluhm?

Done, have fun! :-)
Comment 4 Fedora Update System 2022-03-18 16:08:08 UTC 
FEDORA-EPEL-2022-b32bb7c836 has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-b32bb7c836
Comment 5 Fedora Update System 2022-03-18 20:01:19 UTC 
FEDORA-EPEL-2022-b32bb7c836 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-b32bb7c836

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 6 Fedora Update System 2022-03-25 21:26:52 UTC 
FEDORA-EPEL-2022-b32bb7c836 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.