Your message dated Sat, 28 Nov 2015 22:19:10 +0000 with message-id <e1a2npm-00039l...@franck.debian.org> and subject line Bug#806509: fixed in libept 1.1+nmu3 has caused the Debian Bug report #806509, regarding libept1.5.0 and libept1.4.16: error when trying to install together to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 806509: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806509 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---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 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.
--- End Message ---
--- Begin Message ---Source: libept Source-Version: 1.1+nmu3 We believe that the bug you reported is fixed in the latest version of libept, 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 806...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Julian Andres Klode <j...@debian.org> (supplier of updated libept 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 ftpmas...@ftp-master.debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Format: 1.8 Date: Sat, 28 Nov 2015 20:59:47 +0100 Source: libept Binary: libept-dev libept1.5.0 Architecture: source Version: 1.1+nmu3 Distribution: unstable Urgency: medium Maintainer: Enrico Zini <enr...@debian.org> Changed-By: Julian Andres Klode <j...@debian.org> Description: libept-dev - High-level library for managing Debian package information libept1.5.0 - High-level library for managing Debian package information Closes: 806509 Changes: libept (1.1+nmu3) unstable; urgency=medium . * Non-maintainer upload * Break and replace libept1.4.16 (= 1.0.14+b2) from broken binNMU (Closes: #806509) * Include apt-pkg library version in install file for next APT ABI break * apt/utils/sys.cc: Define O_PATH as 0 if undefined (for !linux) Checksums-Sha1: 5b7bfc13dbeeca9de303c3d984c79778ed89c2ff 1700 libept_1.1+nmu3.dsc 41cd10e1f2ab97e139aa189703cca8b1058bc3e1 616192 libept_1.1+nmu3.tar.xz Checksums-Sha256: b40be07b7c4d1afe6e8ca2e801093d299609d2b6eea9688a271c7c34053d1a17 1700 libept_1.1+nmu3.dsc 59570e68f2fbd81c9f0fb04449fae89c972962017bde616ac32bd216fff5a048 616192 libept_1.1+nmu3.tar.xz Files: 996b1f00345f55744c0e7ba54e1743df 1700 libdevel optional libept_1.1+nmu3.dsc c5e77938f81d4c7b06c7f88c01494334 616192 libdevel optional libept_1.1+nmu3.tar.xz -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJWWgkXAAoJENc8OeVlgLOGeAkP/jq4ppo5t7Nja6QB9E8tna88 BDtQUf+mMLAjLGRuqYEJMfCob6+mK/xZDEPuOouvRDNWLcZTEsDV4zuHKDd4z8jZ qlhd+QvFaSth/YEuJMtrSNfwmb9rdunC5jKUBud3n3xS5sXv90xCJyYYcZzjCaIz 8PbbZyWDTGwsFSqRQZBOIhqtLxHBrNzgA1GE5m3DFaVDWErbWCUTo11akaRlpFB+ RCriuff5x8p67LLipD9jjdL9MB7wv+HozMlzsebyZ/MfQxuT57f/0NMnqVdtQJNX 2D9T9tozJJHaHqRQGuqe+Ec8on1rz3jVNBWAWXO2i7P7nKCokHP+/KRjhMgzjqGN SXoiBKWelnyjUfW4h5BGkaj873XbzbcqKl8R5WYtgyg6nj+h0Kk5foY2K3xbGQgd hFqRNw4h3HResKzEH7VY7NJ/AqHncDbD8g8HxFWwrjchhJB0drFJj4Wr1lZ8M9NA qEhmfpvY74pY93l6TkKcvcoeUTtNSoXQMayWqokjPmMsbW8P5usqw96/yewZ3/wd YW0Le5QxE2Sry6gzSxQ9H1LeRVgks/lvCgMrcsq3taWnr6iQwvHOK9juikjp0QsE HaVjMfIjcGkVdCK3I/wPa50C7iEDmpXgFsssd1t9K/hPGVDc15hKM1bVV0Ml3tFj uW8vKi7zc1zbhDdTwiwk =0WLs -----END PGP SIGNATURE-----
--- End Message ---
