-
Notifications
You must be signed in to change notification settings - Fork 220
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
playbooks: Restore the generation & installation of the Bash completions #1593
Merged
debarshiray
merged 2 commits into
containers:main
from
debarshiray:wip/rishi/playbooks-fedora-bash-completion.pc-00
Nov 14, 2024
Merged
playbooks: Restore the generation & installation of the Bash completions #1593
debarshiray
merged 2 commits into
containers:main
from
debarshiray:wip/rishi/playbooks-fedora-bash-completion.pc-00
Nov 14, 2024
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The package providing /usr/share/pkgconfig/bash-completion.pc changed from bash-completion to bash-completion-devel in Fedora 41 onwards [1]. This meant that the Bash completions were no longer being generated and installed by the CI. [1] Fedora bash-completion commit d1f5dc48c0440cc6 https://src.fedoraproject.org/rpms/bash-completion/c/d1f5dc48c0440cc6 https://bugzilla.redhat.com/show_bug.cgi?id=1457164 containers#1593
debarshiray
force-pushed
the
wip/rishi/playbooks-fedora-bash-completion.pc-00
branch
from
November 12, 2024 22:16
1c5756f
to
2049199
Compare
debarshiray
changed the title
playbooks: Restore the generation & installation of the Bash completion
playbooks: Restore the generation & installation of the Bash completions
Nov 12, 2024
Unlike Fedora, where the package providing bash-completion.pc changed in Fedora 41 onwards [1,2], it hasn't changed in CentOS Stream 9. So, this doesn't change the behaviour of the CI. However, the Fedora Packaging Guidelines recommend using pkgconfig(...) to depend on a *.pc file [3], instead of the name of the package, and there has been a problem on Fedora caused by not doing that. Therefore, it's better to follow the guidelines for consistency and safety. [1] Fedora bash-completion commit d1f5dc48c0440cc6 https://src.fedoraproject.org/rpms/bash-completion/c/d1f5dc48c0440cc6 https://bugzilla.redhat.com/show_bug.cgi?id=1457164 [2] Commit 2049199 containers@204919917e4af528 [3] https://docs.fedoraproject.org/en-US/packaging-guidelines/PkgConfigBuildRequires/ containers#1593
recheck |
debarshiray
deleted the
wip/rishi/playbooks-fedora-bash-completion.pc-00
branch
November 14, 2024 10:47
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The package providing
/usr/share/pkgconfig/bash-completion.pc
changedfrom
bash-completion
tobash-completion-devel
in Fedora 41 onwards [1].This meant that the Bash completions were no longer being generated and
installed by the CI.
[1] Fedora bash-completion commit d1f5dc48c0440cc6
https://src.fedoraproject.org/rpms/bash-completion/c/d1f5dc48c0440cc6
https://bugzilla.redhat.com/show_bug.cgi?id=1457164