Bug 2291024
| Summary: | source package is shell-color-prompt whereas binary is bash-color-prompt | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | ricky.tigg |
| Component: | shell-color-prompt | Assignee: | Jens Petersen <petersen> |
| Status: | CLOSED RAWHIDE | QA Contact: | |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | 45 | CC: | 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
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
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? (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. I checked and indeed https://pagure.io/releng/fedora-scm-requests/issue/55731 I guess this is actually a fbrnch bug/rfe ;-( (Well one can also argue such repo requests should be rejected perhaps...) 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. This bug appears to have been reported against 'rawhide' during the Fedora Linux 42 development cycle. Changing version to 42. I finally opened https://pagure.io/releng/issue/12888 (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. This bug appears to have been reported against 'rawhide' during the Fedora Linux 45 development cycle. Changing version to 45. The source package is now bash-color-prompt in F46 Rawhide for a few weeks. |