Bug 2084286

Summary:	Please branch and build lightdm in epel9
Product:	[Fedora] Fedora EPEL	Reporter:	Troy Dawson <tdawson>
Component:	lightdm	Assignee:	Alternative GTK desktop environments <alt-gtk-de-sig>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	epel9	CC:	alt-gtk-de-sig, christoph.wickert, gp, leigh123linux, raveit65.sun, rdieter
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	lightdm-1.30.0-16.el9	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-05-21 02:07:43 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 Troy Dawson 2022-05-11 19:26:37 UTC

Please branch and build lightdm in epel9.

If you do not wish to maintain lightdm in epel9,
or do not think you will be able to do this in a timely manner,
I would be happy to be a co-maintainer of the package. (FES: tdawson)
Please add me through https://src.fedoraproject.org/rpms/lightdm/adduser

Comment 1 leigh scott 2022-05-11 23:29:53 UTC

Commit rights granted.

Comment 2 Fedora Update System 2022-05-12 14:09:57 UTC

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

Comment 3 Fedora Update System 2022-05-13 02:57:57 UTC

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

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

Comment 4 Fedora Update System 2022-05-21 02:07:43 UTC

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