Bug 2109607

Summary:	Missing EPEL9 package
Product:	[Fedora] Fedora EPEL	Reporter:	luca.magrone
Component:	ddclient	Assignee:	Scott Talbert <swt>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	epel9	CC:	i, jrowens.fedora, swt, thomas, trpost
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ddclient-3.9.1-8.el9	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-08-04 00:37:33 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 luca.magrone 2022-07-21 15:28:37 UTC

Description of problem:
Ddclient is missing from EPEL9 although there should be no problem building the package. I've tried to build the rawhide branch on Copr in epel-9 chroots ad it builds without any problem.

Version-Release number of selected component (if applicable):
EPEL9

Comment 1 Scott Talbert 2022-07-21 23:40:56 UTC

It's missing because no one asked for it.  EPEL9 packages only get created when the maintainer has an interest or people request them.

Comment 2 Fedora Update System 2022-07-25 23:40:55 UTC

FEDORA-EPEL-2022-f6250d8b04 has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-f6250d8b04

Comment 3 Fedora Update System 2022-07-27 03:22:24 UTC

FEDORA-EPEL-2022-f6250d8b04 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-f6250d8b04

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

Comment 4 Fedora Update System 2022-08-04 00:37:33 UTC

FEDORA-EPEL-2022-f6250d8b04 has been pushed to the Fedora EPEL 9 stable repository.
If problem still persists, please make note of it in this bug report.