Bug 1990046

Summary:	Provide ecj for EPEL-8
Product:	[Fedora] Fedora	Reporter:	Stefan Bluhm <fedoraproject.org>
Component:	ecj	Assignee:	Stefan Bluhm <fedoraproject.org>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	35	CC:	akurtako, dbhole, eclipse-sig, omajid
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:	ecj-4.19-3.el8	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-09-02 23:07:45 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Stefan Bluhm 2021-08-04 15:54:49 UTC

Currently, there is no ecj version shipped in EPEL-8 (or RHEL Base/Appstream).

Can you please release an ecj package to EPEL-8?

Thank you.

Comment 1 Ben Cotton 2021-08-10 13:34:51 UTC

This bug appears to have been reported against 'rawhide' during the Fedora 35 development cycle.
Changing version to 35.

Comment 2 Deepak Bhole 2021-08-25 13:51:45 UTC

Sorry for the delay Stefan. I have assigned you as admin to ecj per our email discussion. Re-assigning back.

Comment 3 Fedora Update System 2021-08-25 14:26:37 UTC

FEDORA-EPEL-2021-723d51ca37 has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-723d51ca37

Comment 4 Fedora Update System 2021-08-25 20:23:29 UTC

FEDORA-EPEL-2021-723d51ca37 has been pushed to the Fedora EPEL 8 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-723d51ca37

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

Comment 5 Fedora Update System 2021-09-02 23:07:45 UTC

FEDORA-EPEL-2021-723d51ca37 has been pushed to the Fedora EPEL 8 stable repository.
If problem still persists, please make note of it in this bug report.