Control: reopen -1 On 2022-02-06 18:27:03, Debian Bug Tracking System wrote: > This is an automatic notification regarding your Bug report > which was filed against the python3-jsondiff,cbmc package: > > #1004463: python3-jsondiff,cbmc: File conflict for /usr/bin/jdiff > > It has been closed by Debian FTP Masters <ftpmas...@ftp-master.debian.org> > (reply to Thomas Goirand <z...@debian.org>). > > Their explanation is attached below along with your original report. > If this explanation is unsatisfactory and you have not received a > better one in a separate message then please contact Debian FTP Masters > <ftpmas...@ftp-master.debian.org> (reply to Thomas Goirand <z...@debian.org>) > by > replying to this email. > > > -- > 1004463: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004463 > Debian Bug Tracking System > Contact ow...@bugs.debian.org with problems
> Date: Sun, 06 Feb 2022 18:24:12 +0000 > From: Debian FTP Masters <ftpmas...@ftp-master.debian.org> > To: 1004463-cl...@bugs.debian.org > Subject: Bug#1004463: fixed in python-jsondiff 1.3.1-2 > Reply-To: Thomas Goirand <z...@debian.org> > Message-Id: <e1ngmcq-000iok...@fasolo.debian.org> > > Date: Fri, 28 Jan 2022 03:09:27 +0100 > From: Axel Beckert <a...@debian.org> > To: Debian Bug Tracking System <sub...@bugs.debian.org> > Subject: python3-jsondiff,cbmc: File conflict for /usr/bin/jdiff > Message-ID: <87sft8vcfc....@c6.deuxchevaux.org> > > Package: python3-jsondiff,cbmc > Version: python3-jsondiff/1.3.1-1 > Version: cbmc/5.12-5 > Severity: serious > > Upgrading python3-jsondiff from 1.1.1-4 to 1.3.1-1 fails for me as > follows: > > Preparing to unpack .../python3-jsondiff_1.3.1-1_all.deb ... > Unpacking python3-jsondiff (1.3.1-1) over (1.1.1-4) ... > dpkg: error processing archive > /var/cache/apt/archives/python3-jsondiff_1.3.1-1_all.deb (--unpack): > trying to overwrite '/usr/bin/jdiff', which is also in package cbmc 5.12-5 > > (Note: There might be more file conflict than this one between those two > packages, because dpkg already aborts on the first conflict and doesn't > report potential further ones. Typical example: program and man pages) > > Since I suspect that these two variants of "jdiff" do completely > different things, it's probably no option to use the alternatives system > in this case. > > Which leaves the following options: > > * Renaming the file in either or both packages. > > * Making the packages conflict with each other. (Suffices to be fixed in > one package.) No, this is not an option. From the policy [1]: "the two different packages must not install programs with different functionality but with the same filenames. ... If this case happens, one of the programs must be renamed." The packages provide programs named jdiff with different functionality. Hence, one of them needs to be renamed. If no conclusion can be reached, both of them need to be renamed. Cheers [1] https://www.debian.org/doc/debian-policy/ch-files.html#s-binaries > > -- System Information: > Debian Release: bookworm/sid > APT prefers unstable > APT policy: (990, 'unstable'), (600, 'testing'), (500, 'unstable-debug'), > (500, 'buildd-unstable'), (110, 'experimental'), (1, 'experimental-debug'), > (1, 'buildd-experimental') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 5.15.0-2-amd64 (SMP w/4 CPU threads) > Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set > Shell: /bin/sh linked to /bin/dash > Init: sysvinit (via /sbin/init) > LSM: AppArmor: enabled > > Versions of packages python3-jsondiff depends on: > ii python3 3.9.8-1 > > python3-jsondiff recommends no packages. > > python3-jsondiff suggests no packages. > > -- no debconf information -- Sebastian Ramacher
