Hi,

your packages crm114 and crmsh both install a program named "crm",
although in different components of the PATH.

As this is confusing and a possible source of bugs, policy bug
#1075856 wants to outlaw this.

Please find a solution for your packages. Ideas:
1) if one of the programs is an internal implementation detail of
the package, install it into a private path in /usr/lib instead.
2) rename one of the programs
3) rename both of the programs
4) if allowed by policy, use Conflicts:.

Thanks,
Chris

Not sure if there is a good solution here since the documentation
and scripts for both programs seem to assume the crm binary name,
for example:

https://crmsh.github.io/start-guide/

Well, crm114 is long time abandonware upstream and according to the
popularity contest not much popular in Debian.  So I think it’s better
to leave crmsh untouched and solve the problem on the crm114 side.
Either by making it conflicting with crmsh or by renaming the binary to
crm114.  The latter could upset users because their copied example
scripts with the original shebangs would stop working; maybe the
conflict would be better then, I guess there is a good chance that
nobody uses both crmsh and crm114 on the same system.

Regards,
Milan

Thanks for the update. Maybe the binary can be renamed to crm114 and
NEWS.Debian can list dpkg-divert as an option if someone needs to keep
it under the original name?

    VV> Maybe the binary can be renamed to crm114 and NEWS.Debian can
    VV> list dpkg-divert as an option if someone needs to keep it under
    VV> the original name?

This is the cleanest option.  I thought about the fact that all the
crm114 users would be impacted while in case nobody uses both crm114 and
crmsh on the same machine (which is quite likely I guess), making the
packages simply conflicting wouldn’t impact anybody.  But it’s probably
better to go with the cleaner option, it’s a one-time change after all.

Hi all,

Chris mentioned this bug in reply to me on #1104051 so I'm putting my 2p
in here.

We need to consider what is the best course of action for Trixie, and
then longer-term. Trixie hard freeze is 2025-05-15 (13 days time).

I agree that the best longer-term solution is to rename crm114 (slightly
grumpy, since it's been established at bin/crm for far longer). However,
I think implementing a rename at this point and having effectively zero
time for a transition to soak before the freeze is not great for users.

How about adding a conflict and a NEWS.Debian entry for Trixie,
explaining the conflict and that for trixie+1 it'll be renamed (and no
conflict)?

    JD> We need to consider what is the best course of action for
    JD> Trixie, and then longer-term. Trixie hard freeze is 2025-05-15
    JD> (13 days time).

    JD> I agree that the best longer-term solution is to rename crm114
    JD> (slightly grumpy, since it's been established at bin/crm for far
    JD> longer). However, I think implementing a rename at this point
    JD> and having effectively zero time for a transition to soak before
    JD> the freeze is not great for users.

    JD> How about adding a conflict and a NEWS.Debian entry for Trixie,
    JD> explaining the conflict and that for trixie+1 it'll be renamed
    JD> (and no conflict)?

Thank you for the suggestion.  That’d be fine from my side — my guess is
the conflict won’t bother anybody, so no immediate need to hurry.  And
renaming is still what should happen eventually.

    JD> How about adding a conflict and a NEWS.Debian entry for Trixie,
    JD> explaining the conflict and that for trixie+1 it'll be renamed
    JD> (and no conflict)?

Done.  Keeping the bug open, until the binary is renamed.

Control: severity -1 serious

I'm raising the severity of these bugs to serious, so forky will be
released without these policy violations.

Thanks,
Chris

I have uploaded crmsh with Conflicts also, so I guess the remaining
step is the binary rename in crm114.

We believe that the bug you reported is fixed in the latest version of
crm114, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1098983@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Milan Zamazal <pdm@debian.org> (supplier of updated crm114 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)
Format: 1.8
Date: Sat, 21 Feb 2026 19:45:17 +0100
Source: crm114
Architecture: source
Version: 20100106-12
Distribution: unstable
Urgency: medium
Maintainer: Milan Zamazal <pdm@debian.org>
Changed-By: Milan Zamazal <pdm@debian.org>
Closes: 1098983
Changes:
 crm114 (20100106-12) unstable; urgency=medium
 .
   * `crm' binary renamed to `crm114' to avoid the conflict with crmsh;
     closes: #1098983.
Checksums-Sha1:
 d33ca6d023b6941d5f3cb98ee5c4b9a7dffd63df 1750 crm114_20100106-12.dsc
 59d537b474b6817f2ec18ae10cdece6c954991f6 38792 crm114_20100106-12.debian.tar.xz
 e406d28278226abb820831399d2d6ebc65f94e0c 6306 crm114_20100106-12_amd64.buildinfo
Checksums-Sha256:
 02e6d44973b5e22bc5ecda02b37ce4a081cc3057892f1fbcd725a8c63b6eeb45 1750 crm114_20100106-12.dsc
 66013474331aeacbd4d46b2441e65b22ad469048735481238dbff2b43c31f1a1 38792 crm114_20100106-12.debian.tar.xz
 1fc408d7bfed5d3e14d89932bf1e6e121fe4472aa700d05517af28974e7789c9 6306 crm114_20100106-12_amd64.buildinfo
Files:
 c74b0315812604cf7bd6eba6cb74a291 1750 mail optional crm114_20100106-12.dsc
 cda8d3cc2edf2bd9acd0d4fc19234544 38792 mail optional crm114_20100106-12.debian.tar.xz
 a7d930d68e852fb862ce40f12c635c0e 6306 mail optional crm114_20100106-12_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEPv4PPfDJjii4qBxHFNAaCK/Ym+MFAmmaImwACgkQFNAaCK/Y
m+OUMA//WZJqkOW8xqr46geAHDIlzemaarwhcKUKiA1d5uyYUP1L4g9AGLTWsnPc
H1cT1CokMHYLRE+e8YkB4FuX689uEfQRtdW9t9KerSm9u4/OW2kKZC0dBYbdRC3d
0kwy9IU/+qabUDeYNPswGKBQD0NSnzmPpYMKB56sk2HvrhMrf1SrGYkYEB+QOoYB
cHsCaCinv7RktQ3Q7bvB5pqsQrAlFStFmTFUi8ygxU7+lhj2ZxHsQTeeujDQdEy1
/CMGPQY6OaRb/t5HiRPNrcgeuUJT2DxKMRiOQwFBavB4hbRRD2IEc+fGEaTVN3GX
ZODywXGJMsbrdo7irlt8G4v88Z0aQoNUS5EP/nn96bm3u1XmowXwCnx45e8Wpifz
PiOLvicvIaJkCChYad3qnzG7rmHP8GJjSBTOAEQ9+23/WKh7ShFCCnFLeV6iTBNO
++PqQE9TyUrVSdLU/OmE2xunbo1KZbSB4mcNRIel5Ebf38jA8U+nEwkEeNIVJ7UH
yFpgdd+YXoodXv4R1XDfhrg0M0exBU1hhMDF1wjVgMJQCFIP7YgZkaMcqV7tGDZo
weWcpvi6Vpl6Quz1UkzTJYgI7Rrz0yORlTmp0aS97RT7IRtcpIdYXKPQUSxIYhTA
5RSQutVhXqt9a/dtqhyeEoLpF0EA6vWcmZCQYDAvusdauXytJmM=
=TZBe
-----END PGP SIGNATURE-----