Bug 2271833

Summary: Update package in EPEL8 / possible?
Product: [Fedora] Fedora EPEL Reporter: Leon Fauster <leonfauster>
Component: shell-color-promptAssignee: Jens Petersen <petersen>
Status: CLOSED ERRATA QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: epel8CC: petersen
Target Milestone: ---Flags: petersen: mirror+
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: shell-color-prompt-0.4-1.el8 Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2025-08-07 01:28:23 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 Leon Fauster 2024-03-27 13:29:24 UTC
Thanks for this new package in EPEL!

Description of problem:

Current version in EPEL8 is shell-color-prompt-0.1-6.el8

Is it possible to rebase it to the same version of EPEL9?
(-> shell-color-prompt-0.4-1.el9)

Comment 1 Jens Petersen 2025-04-07 06:01:13 UTC
Yes, should be possible - sorry for the long delay

Comment 2 Jens Petersen 2025-07-10 05:53:17 UTC
I tested a bit and it seems to work okay, so going ahead.

Comment 3 Fedora Update System 2025-07-10 06:22:58 UTC
FEDORA-EPEL-2025-0a390ac539 (shell-color-prompt-0.4-1.el8) has been submitted as an update to Fedora EPEL 8.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-0a390ac539

Comment 4 Fedora Update System 2025-07-10 14:41:08 UTC
FEDORA-EPEL-2025-0a390ac539 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-2025-0a390ac539

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

Comment 5 Fedora Update System 2025-08-07 01:28:23 UTC
FEDORA-EPEL-2025-0a390ac539 (shell-color-prompt-0.4-1.el8) has been pushed to the Fedora EPEL 8 stable repository.
If problem still persists, please make note of it in this bug report.