-
Notifications
You must be signed in to change notification settings - Fork 386
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
secret-tool completion file conflicting with upstream file #1317
Comments
Same issue here on Mageia Cauldron! |
Interesting. Per https://github.com/GNOME/libsecret/tree/0.20.5/bash-completion it looks like upstream completion has been available since 0.20.5, so about 3 years, but this is the first time I've heard of the conflict. Our standard action in cases like this is to deprecate our completion, which in this case is a bit of a shame as it seems much more featureful than the upstream one. Perhaps someone would be interested in submitting our goodies for inclusion there? |
Anyway in the meantime, I suggest asking for a fix from your distro packagers, either the libsecret or bash-completion one, so that only one of them ships the completion in the package. |
Describe the bug
Since libsecret 0.21.6, the completion file secret-tool is include and installed in the very same directory as bash-completion. For downstream distros this may cause file conflicts blocking both packages to be installed at the same time. For instance, see
this issuethis issue in Arch Linux forlibsecretbash-completion package.EDIT: issue moved from libsecret to bash-completion
Should the secret-tool completion file be removed from bash-completion, since the upstream now ships it?
To reproduce
On Arch Linux:
Expected behavior
No conflict between libsecret and bash-completion, allowing both to be installed.
Versions (please complete the following information)
echo "$BASH_VERSION"
: 5.2.37(1)-release(IFS=.; echo "${BASH_COMPLETION_VERSINFO[*]}")
: 2.15.0Additional context
Debug trace
The text was updated successfully, but these errors were encountered: