Bug 2291024

Summary: source package is shell-color-prompt whereas binary is bash-color-prompt
Product: [Fedora] Fedora Reporter: ricky.tigg
Component: shell-color-promptAssignee: Jens Petersen <petersen>
Status: CLOSED RAWHIDE QA Contact:
Severity: low Docs Contact:
Priority: low    
Version: 45CC: petersen
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: bash-color-prompt-0.96.1-1.fc46 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2026-10-02 13:27:16 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 ricky.tigg 2024-06-08 15:02:04 UTC
Suggestion: Hello. The name of the component to customize the Bash Shell colour prompt varies depending on whether it is hosted on domains *.fedoraproject.org, as "shell-color-prompt" or on the Fedora infrastructure, as "bash-color-prompt". This is obviously a source of confusion. For the sake of consistency and coherence, wouldn't it have been better if the component name didn't vary?

$ rpm -qi bash-color-prompt | grep -E '^URL|^Bug URL'
URL    : https://src.fedoraproject.org/rpms/shell-color-prompt
Bug URL: https://bugz.fedoraproject.org/shell-color-prompt

$ dnf rq --installed --qf 'v. %{version} | %{summary}' bash-color-prompt
v. 0.4.1 | Color prompt for bash shell

Comment 1 Jens Petersen 2024-06-10 06:34:34 UTC
Well it is simply the difference between the source and binary package names,
so yea what can I say it is slightly confusing perhaps indeed.
TBH I slightly regret renaming the source during the review process:
the idea was that in the future other shells might also be supported,
but it's complicated enough at least for bash that it is non-trivial to add and maintain more shells 
and the zsh ecosystem has a lot more support for customization anyway.

I may leave just this open for some time, but I have no immediate plans to rename the source package anytime soon.

Having said all that it there are many packages where the connection between the source and binary names is not self-evident.
So yeah one has to check with `rpm -qi ...` etc.

$ rpm -q --qf "%{SOURCERPM}\n" bash-color-prompt 
shell-color-prompt-0.4.2-1.fc41.src.rpm

Comment 2 ricky.tigg 2024-06-10 11:48:17 UTC
Worth noting: On this platform, the description of this component is marked "NA", indicating that it was not yet defined. Again as a suggestion, wouldn't it have been better to have one defined?

Comment 3 Jens Petersen 2024-06-13 11:24:32 UTC
(In reply to ricky.tigg from comment #2)
> Worth noting: On this platform, the description of this component is marked
> "NA", indicating that it was not yet defined. Again as a suggestion,
> wouldn't it have been better to have one defined?

Good catch, that might be my fault possibly: not sure how to fix that though.

Comment 4 Jens Petersen 2024-07-05 10:03:05 UTC
I checked and indeed https://pagure.io/releng/fedora-scm-requests/issue/55731

I guess this is actually a fbrnch bug/rfe ;-(

Comment 5 Jens Petersen 2024-07-05 10:09:55 UTC
(Well one can also argue such repo requests should be rejected perhaps...)

Comment 6 Jens Petersen 2024-07-05 10:16:02 UTC
Actually I am wrong - I don't think it is related to fbrnch.
The request does have a Summary field, so I suspect maybe
the repo request was not 100% processed correctly:
this sometimes happens unfortunately, or the bz data is messed up perhaps.

I will try to work with releng to rectify this later.

Comment 7 Aoife Moloney 2025-02-26 13:03:41 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 42 development cycle.
Changing version to 42.

Comment 8 Jens Petersen 2025-08-17 12:22:59 UTC
I finally opened https://pagure.io/releng/issue/12888

Comment 9 Jens Petersen 2025-09-12 02:30:22 UTC
(In reply to Jens Petersen from comment #8)
> I finally opened https://pagure.io/releng/issue/12888

This has now been resolved by Release Engineering.

Comment 10 Aoife Moloney 2026-08-17 13:18:31 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 45 development cycle.
Changing version to 45.

Comment 11 Jens Petersen 2026-10-02 13:27:16 UTC
The source package is now bash-color-prompt in F46 Rawhide for a few weeks.