Bug 2035960

Summary:	Please branch and build neofetch in epel9
Product:	[Fedora] Fedora EPEL	Reporter:	Alessio <alciregi>
Component:	neofetch	Assignee:	Kees de Jong <keesdejong+dev>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	epel9	CC:	keesdejong+dev
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	neofetch-7.1.0-7.el9	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-02-22 03:16:46 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 Alessio 2021-12-28 22:25:28 UTC

Please branch and build neofetch in epel9.

If you do not wish to maintain neofetch 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.

Comment 1 Kees de Jong 2022-01-03 10:15:41 UTC

I'll have a look this month. I'll have to check if packaging rules have changed with EPEL9 or not. Otherwise it will be easy to create a version for EPEL9 since Neofetch is just a Bash script.

Comment 2 Fedora Update System 2022-02-13 06:26:42 UTC

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

Comment 3 Fedora Update System 2022-02-14 01:44:34 UTC

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

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

Comment 4 Fedora Update System 2022-02-22 03:16:46 UTC

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