Re: Bug#1005858: gh,gitsome: File conflict, both ship /usr/bin/gh
Hi everyone,
On Sat, Feb 26, 2022 at 7:09 PM Paul Wise <pabs@debian.org> wrote:
>
> Control: forwarded -1 https://github.com/donnemartin/gitsome/issues/177
>
> On Sat, 26 Feb 2022 23:43:14 +0800 SZ Lin (林上智) wrote:
>
> > The "gitsome" has used "gh" since 2017, and thus would you mind renaming
> > the "gh" in your package to avoid the conflict issue?
>
> Since gh is the official GitHub client, probably it should retain "gh"
> and gitsome should move to "git some" or similar, as I have suggested
> in the above upstream issue. The only commentor there agreed with me.
Thank you all for the discussion and attempt at resolving the filename conflict.
Judging from gitsome's GitHub repo being left stagnant since May 2019,
with Issues and PRs unanswered, despite the fact that upstream author
is still active daily on GitHub, I doubt we'll see a reply from
gitsome's author anytime soon.
Automation scripts are relying on the GitHub CLI command to be named
as "gh", so renaming /usr/bin/gh in "gh" to something else is out of
the question too.
Rather than keeping this "Serious" bug open and keeping both gitsome
and gh out of Debian testing, I think the simple solution of having gh
"Conflicts: gitsome", which is one of the option specified in
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-conflicts,
would suffice for now, allowing both packages to (re-)enter testing in
the meantime.
SZ, if you think the use of alternatives (such that both the gitsome
and gh packages can be installed simultaneously) is a better solution,
I'd be happy to work something out with you too.
Cheers,
Anthony
Reply to: