Le 02/09/2022 à 01:10, Guillem Jover a écrit :
Hi!
On Wed, 2022-08-10 at 01:29:27 +0200, Guillem Jover wrote:
[ The bug has been (correctly) bumped back to serious. Sorry that I
have not engaged about this bug in the past, but the reply to simply
ignore policy looked rather off-putting, I just noticed the reply
below, which seemed encouraging! :) ]
On Sat, 2019-01-26 at 11:20:13 +0100, Sylvestre Ledru wrote:
As we shipped the previous release with this bug, we are close to
the freeze and there is not easy fix,
I propose that we fix this issue for the next stable release.
Could you please rename the archanist /usr/bin/arc into
/usr/bin/arcanist? Or if that's not feasible, then stop installing the
symlink in PATH, and document that users might want to add the /usr/share
/arcanist/bin/ into their own PATH? Or do both?
Renaming the binary from the arc package, which matches the package
name itself, seems unfair, as it has existed upstream and has been in
the Debian archive for way way longer, and in addition the idea of
potentially having a binary package arc with a non-arc program, and
arcanist providing an arc program seems rather confusing and just
wrong. :)
Otherwise, all these package will get removed in the coming days. So I'd
also appreciate if you could reassign these bugs to arcanist.
So we have reached the point at which arc is getting autoremoved from
testing as the RC is still filed against it too. :(
Could some arcanist maintainer please check this, and ideally agree to
reassign this bug to arcanist? If necessary I'm willing to prepare a
patch for arcanist to stop installing as bin/arc, as described above,
if this would expedite things.
I don't think renaming is the right approach against an MS-DOS software (and I
still think
that Debian's policy is too binary for this).
However, as:
* phabricator is dying
* Richard, Christoph and myself didn't show a strong interest to keep it alive
(it is currently broken in unstable).
Please do what you want. ;)
Cheers
Sylvestre
