Bug#806509: libept1.5.0 and libept1.4.16: error when trying to install together
Control: subscribe -1 j...@debian.org On Sat, Nov 28, 2015 at 08:26:45AM +0100, Ralf Treinen wrote: > Package: libept1.4.16,libept1.5.0 > Version: libept1.4.16/1.0.14+b2 > Version: libept1.5.0/1.1+nmu2 > Severity: serious > User: trei...@debian.org > Usertags: edos-file-overwrite > > Date: 2015-11-28 > 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: That got ugly temporarily due to a binNMU that went wrong and produced a library with the wrong soname. We could probably Replace libept1.4.16 (= 1.0.14+b2) or something (and conflict with that build). The broken libept binNMU was in unstable for less than 24 hours though (excluding non-Linux ports, for which it still exists, because the current build FTBFS due to O_PATH being undefined, which is easy to fix). What do you think? -- Julian Andres Klode - Debian Developer, Ubuntu Member See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/. When replying, only quote what is necessary, and write each reply directly below the part(s) it pertains to (`inline'). Thank you.
Bug#806509: libept1.5.0 and libept1.4.16: error when trying to install together
Package: libept1.4.16,libept1.5.0 Version: libept1.4.16/1.0.14+b2 Version: libept1.5.0/1.1+nmu2 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2015-11-28 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 ... 10925 files and directories currently installed.) Preparing to unpack .../gcc-5-base_5.2.1-26_amd64.deb ... Unpacking gcc-5-base:amd64 (5.2.1-26) ... Setting up gcc-5-base:amd64 (5.2.1-26) ... (Reading database ... 10932 files and directories currently installed.) Preparing to unpack .../libstdc++6_5.2.1-26_amd64.deb ... Unpacking libstdc++6:amd64 (5.2.1-26) over (4.8.2-19) ... Processing triggers for libc-bin (2.19-22) ... Setting up libstdc++6:amd64 (5.2.1-26) ... Processing triggers for libc-bin (2.19-22) ... (Reading database ... 10946 files and directories currently installed.) Preparing to unpack .../archives/apt_1.1.1_amd64.deb ... Unpacking apt (1.1.1) over (1.0.4) ... Selecting previously unselected package libapt-pkg5.0:amd64. Preparing to unpack .../libapt-pkg5.0_1.1.1_amd64.deb ... Unpacking libapt-pkg5.0:amd64 (1.1.1) ... Processing triggers for libc-bin (2.19-22) ... Processing triggers for man-db (2.7.5-1) ... Setting up libapt-pkg5.0:amd64 (1.1.1) ... Processing triggers for libc-bin (2.19-22) ... (Reading database ... 10979 files and directories currently installed.) Preparing to unpack .../aptitude_0.7.4-2_amd64.deb ... Unpacking aptitude (0.7.4-2) over (0.6.10-1) ... Preparing to unpack .../aptitude-common_0.7.4-2_all.deb ... Unpacking aptitude-common (0.7.4-2) over (0.6.10-1) ... Selecting previously unselected package libboost-iostreams1.58.0:amd64. Preparing to unpack .../libboost-iostreams1.58.0_1.58.0+dfsg-4_amd64.deb ... Unpacking libboost-iostreams1.58.0:amd64 (1.58.0+dfsg-4) ... Processing triggers for man-db (2.7.5-1) ... Processing triggers for libc-bin (2.19-22) ... (Reading database ... 10977 files and directories currently installed.) Removing libcwidget3:amd64 (0.5.17-1) ... Removing libsigc++-2.0-0c2a:amd64 (2.4.1-1) ... Processing triggers for libc-bin (2.19-22) ... Selecting previously unselected package libsigc++-2.0-0v5:amd64. (Reading database ... 10924 files and directories currently installed.) Preparing to unpack .../libsigc++-2.0-0v5_2.6.2-1_amd64.deb ... Unpacking libsigc++-2.0-0v5:amd64 (2.6.2-1) ... Selecting previously unselected package libcwidget3v5:amd64. Preparing to unpack .../libcwidget3v5_0.5.17-4_amd64.deb ... Unpacking libcwidget3v5:amd64 (0.5.17-4) ... Processing triggers for libc-bin (2.19-22) ... (Reading database ... 10977 files and directories currently installed.) Removing libept1.4.12:amd64 (1.0.12) ... Removing libxapian22 (1.2.17-1) ... Processing triggers for libc-bin (2.19-22) ... Selecting previously unselected package libxapian22v5. (Reading database ... 10964 files and directories currently installed.) Preparing to unpack .../libxapian22v5_1.2.21-1.2_amd64.deb ... Unpacking libxapian22v5 (1.2.21-1.2) ... Selecting previously unselected package libept1.4.16:amd64. Preparing to unpack .../libept1.4.16_1.0.14+b2_amd64.deb ... Unpacking libept1.4.16:amd64 (1.0.14+b2) ... Selecting previously unselected package libept1.5.0:amd64. Preparing to unpack .../libept1.5.0_1.1+nmu2_amd64.deb ... Unpacking libept1.5.0:amd64 (1.1+nmu2) ... dpkg: error processing archive /var/cache/apt/archives/libept1.5.0_1.1+nmu2_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libept.so.1.aptpkg5.0', which is also in package libept1.4.16:amd64 1.0.14+b2 Processing triggers for libc-bin (2.19-22) ... Errors were encountered while processing: /var/cache/apt/archives/libept1.5.0_1.1+nmu2_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/lib/x86_64-linux-gnu/libept.so.1.aptpkg5.0 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
