On Sat, Jul 18, 2020 at 03:36:48PM -0400, Boyuan Yang wrote: > X-Debbugs-CC: debian-fo...@lists.debian.org m...@debian.org > > On Thu, 16 Jul 2020 23:19:31 +0200 Andreas Beckmann <a...@debian.org> > wrote: > > Package: afdko-bin > > Version: 3.4.0+dfsg1-2 > > Severity: serious > > > > Preparing to unpack .../afdko-bin_3.4.0+dfsg1-2_amd64.deb ... > > Unpacking afdko-bin (3.4.0+dfsg1-2) ... > > dpkg: error processing archive /var/cache/apt/archives/afdko- > bin_3.4.0+dfsg1-2_amd64.deb (--unpack): > > trying to overwrite '/usr/bin/tx', which is also in package > transifex-client 0.13.9-1 > > Errors were encountered while processing: > > /var/cache/apt/archives/afdko-bin_3.4.0+dfsg1-2_amd64.deb > > > > If the conflicting situation cannot be resolved then, as > > last resort, the two packages have to declare a mutual > > Conflict. > > AFAICT a mutual conflict could be the only reasonable solution. @mwei > what do you think?
The policy is very clear: #10.1. # Two different packages must not install programs with different # functionality but with the same filenames. (The case of two programs # having the same functionality but different implementations is handled # via “alternatives” or the “Conflicts” mechanism. See Maintainer # Scripts and Conflicting binary packages - Conflicts respectively.) If # this case happens, one of the programs must be renamed. The # maintainers should report this to the "debian-devel" mailing list and # try to find a consensus about which program will have to be renamed. # If a consensus cannot be reached, *both* programs must be renamed. Thus, a mutual conflict is not allowed. Two random packages without a relation are not expected to conflict: there's no reason someone who hacks on some software that uses Transifex to manage their translation wouldn't also want to deal with fonts -- we're in the "breaks unrelated software" land. This issue pops up on debian-devel quite often, and the consensus is that exceptions shouldn't be given. Major cases: "node": axnode vs node.js, "git" vs gnuit. Meow! -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ ⢿⡄⠘⠷⠚⠋⠀ It's time to migrate your Imaginary Protocol from version 4i to 6i. ⠈⠳⣄⠀⠀⠀⠀
