Package: libvolk-bin,libvolk1.0-bin Version: libvolk-bin/3.7.5-5 Version: libvolk1.0-bin/1.0-1 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite
Date: 2015-06-25 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: Selecting previously unselected package gcc-5-base:amd64. (Reading database ... 10902 files and directories currently installed.) Preparing to unpack .../gcc-5-base_5.1.1-12_amd64.deb ... Unpacking gcc-5-base:amd64 (5.1.1-12) ... Setting up gcc-5-base:amd64 (5.1.1-12) ... (Reading database ... 10909 files and directories currently installed.) Preparing to unpack .../libstdc++6_5.1.1-12_amd64.deb ... Unpacking libstdc++6:amd64 (5.1.1-12) over (4.8.2-19) ... Setting up libstdc++6:amd64 (5.1.1-12) ... Processing triggers for libc-bin (2.19-18) ... Selecting previously unselected package libdb5.3:amd64. (Reading database ... 10923 files and directories currently installed.) Preparing to unpack .../libdb5.3_5.3.28-9_amd64.deb ... Unpacking libdb5.3:amd64 (5.3.28-9) ... Selecting previously unselected package libpython2.7-minimal:amd64. Preparing to unpack .../libpython2.7-minimal_2.7.10-2_amd64.deb ... Unpacking libpython2.7-minimal:amd64 (2.7.10-2) ... Selecting previously unselected package python2.7-minimal. Preparing to unpack .../python2.7-minimal_2.7.10-2_amd64.deb ... Unpacking python2.7-minimal (2.7.10-2) ... Selecting previously unselected package python-minimal. Preparing to unpack .../python-minimal_2.7.9-1_amd64.deb ... Unpacking python-minimal (2.7.9-1) ... Selecting previously unselected package mime-support. Preparing to unpack .../mime-support_3.58_all.deb ... Unpacking mime-support (3.58) ... Selecting previously unselected package libexpat1:amd64. Preparing to unpack .../libexpat1_2.1.0-6+b3_amd64.deb ... Unpacking libexpat1:amd64 (2.1.0-6+b3) ... Selecting previously unselected package libffi6:amd64. Preparing to unpack .../libffi6_3.1-2+b2_amd64.deb ... Unpacking libffi6:amd64 (3.1-2+b2) ... Selecting previously unselected package libpython2.7-stdlib:amd64. Preparing to unpack .../libpython2.7-stdlib_2.7.10-2_amd64.deb ... Unpacking libpython2.7-stdlib:amd64 (2.7.10-2) ... Selecting previously unselected package python2.7. Preparing to unpack .../python2.7_2.7.10-2_amd64.deb ... Unpacking python2.7 (2.7.10-2) ... Selecting previously unselected package libpython-stdlib:amd64. Preparing to unpack .../libpython-stdlib_2.7.9-1_amd64.deb ... Unpacking libpython-stdlib:amd64 (2.7.9-1) ... Processing triggers for man-db (2.7.0.2-5) ... Setting up libpython2.7-minimal:amd64 (2.7.10-2) ... Setting up python2.7-minimal (2.7.10-2) ... Setting up python-minimal (2.7.9-1) ... Selecting previously unselected package python. (Reading database ... 11717 files and directories currently installed.) Preparing to unpack .../python_2.7.9-1_amd64.deb ... Unpacking python (2.7.9-1) ... Selecting previously unselected package libboost-system1.55.0:amd64. Preparing to unpack .../libboost-system1.55.0_1.55.0+dfsg-3_amd64.deb ... Unpacking libboost-system1.55.0:amd64 (1.55.0+dfsg-3) ... Selecting previously unselected package libboost-filesystem1.55.0:amd64. Preparing to unpack .../libboost-filesystem1.55.0_1.55.0+dfsg-3_amd64.deb ... Unpacking libboost-filesystem1.55.0:amd64 (1.55.0+dfsg-3) ... Selecting previously unselected package libboost-program-options1.55.0:amd64. Preparing to unpack .../libboost-program-options1.55.0_1.55.0+dfsg-3_amd64.deb ... Unpacking libboost-program-options1.55.0:amd64 (1.55.0+dfsg-3) ... Selecting previously unselected package libboost-test1.55.0:amd64. Preparing to unpack .../libboost-test1.55.0_1.55.0+dfsg-3_amd64.deb ... Unpacking libboost-test1.55.0:amd64 (1.55.0+dfsg-3) ... Selecting previously unselected package liborc-0.4-0:amd64. Preparing to unpack .../liborc-0.4-0_1%3a0.4.24-1_amd64.deb ... Unpacking liborc-0.4-0:amd64 (1:0.4.24-1) ... Selecting previously unselected package libvolk0.0.0:amd64. Preparing to unpack .../libvolk0.0.0_3.7.5-5_amd64.deb ... Unpacking libvolk0.0.0:amd64 (3.7.5-5) ... Selecting previously unselected package libvolk-bin. Preparing to unpack .../libvolk-bin_3.7.5-5_amd64.deb ... Unpacking libvolk-bin (3.7.5-5) ... Selecting previously unselected package libvolk1.0:amd64. Preparing to unpack .../libvolk1.0_1.0-1_amd64.deb ... Unpacking libvolk1.0:amd64 (1.0-1) ... Selecting previously unselected package libvolk1.0-bin. Preparing to unpack .../libvolk1.0-bin_1.0-1_amd64.deb ... Unpacking libvolk1.0-bin (1.0-1) ... dpkg: error processing archive /var/cache/apt/archives/libvolk1.0-bin_1.0-1_amd64.deb (--unpack): trying to overwrite '/usr/bin/volk-config-info', which is also in package libvolk-bin 3.7.5-5 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Processing triggers for man-db (2.7.0.2-5) ... Errors were encountered while processing: /var/cache/apt/archives/libvolk1.0-bin_1.0-1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) This is a serious bug as it makes installation fail, and violates sections 7.6.1 and 10.1 of the policy. An optimal solution would consist in only one of the packages installing that file, and renaming or removing the file in the other package. Depending on the circumstances you might also consider Replace relations or file diversions. If the conflicting situation cannot be resolved then, as a last resort, the two packages have to declare a mutual Conflict. Please take into account that Replaces, Conflicts and diversions should only be used when packages provide different implementations for the same functionality. Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync): /usr/bin/volk-config-info /usr/bin/volk_modtool /usr/bin/volk_profile /usr/share/man/man1/volk-config-info.1.gz /usr/share/man/man1/volk_modtool.1.gz /usr/share/man/man1/volk_profile.1.gz This bug has been filed against both packages. If you, the maintainers of the two packages in question, have agreed on which of the packages will resolve the problem please reassign the bug to that package. You may then also register in the BTS that the other package is affected by the bug. -Ralf. PS: for more information about the detection of file overwrite errors of this kind see http://qa.debian.org/dose/file-overwrites.html. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
