Your message dated Wed, 10 Jan 2018 17:23:34 +0000 with message-id <e1ezk6a-0002v8...@fasolo.debian.org> and subject line Bug#886842: fixed in libreswan 3.22-4 has caused the Debian Bug report #886842, regarding libreswan,strongswan-libcharon: both ship /usr/lib/ipsec/_updown 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.) -- 886842: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886842 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: libreswan,strongswan-libcharon Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Control: found -1 5.6.1-3 Control: found -1 3.22-3 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 strongswan-libcharon. Preparing to unpack .../strongswan-libcharon_5.6.1-3_amd64.deb ... Unpacking strongswan-libcharon (5.6.1-3) ... dpkg: error processing archive /var/cache/apt/archives/strongswan-libcharon_5.6.1-3_amd64.deb (--unpack): trying to overwrite '/usr/lib/ipsec/_updown', which is also in package libreswan 3.22-3 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/strongswan-libcharon_5.6.1-3_amd64.deb 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/ipsec/_updown This bug is assigned to 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 also register in the BTS that the other package is affected by the bug. Cheers, Andreas PS: for more information about the detection of file overwrite errors of this kind see https://qa.debian.org/dose/file-overwrites.html
libreswan=3.22-3_strongswan-libcharon=5.6.1-3.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---Source: libreswan Source-Version: 3.22-4 We believe that the bug you reported is fixed in the latest version of libreswan, 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 886...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Daniel Kahn Gillmor <d...@fifthhorseman.net> (supplier of updated libreswan 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: Wed, 10 Jan 2018 12:01:37 -0500 Source: libreswan Binary: libreswan Architecture: source Version: 3.22-4 Distribution: unstable Urgency: medium Maintainer: Daniel Kahn Gillmor <d...@fifthhorseman.net> Changed-By: Daniel Kahn Gillmor <d...@fifthhorseman.net> Description: libreswan - Internet Key Exchange daemon Closes: 886842 Changes: libreswan (3.22-4) unstable; urgency=medium . * conflict with strongswan-libcharon (Closes: #886842) * Standards-Version: bump to 4.1.3 (no changes needed) * move to debhelper 11 * Vcs: move to salsa.debian.org * clean up lintian overrides Checksums-Sha1: aa34e538fc77d660ac71e1738ef4dc69e1a6dc9a 2568 libreswan_3.22-4.dsc 80a2cbb73d6aa8eb2bfa9cff24a56f3c08791277 16412 libreswan_3.22-4.debian.tar.xz ee7b77ff3c84b9af4551338bc451ea9919a5a618 10529 libreswan_3.22-4_amd64.buildinfo Checksums-Sha256: 6ce399419624a54bf72f2ed989fa03ee2dba23bb452c6b8dbfa6f2b6d647e8fe 2568 libreswan_3.22-4.dsc 2aeb78ea1ef7f642abd29de0c8f98e5998f45b6d631fab64e05e9a15c0bdd69b 16412 libreswan_3.22-4.debian.tar.xz a09227623150464b259b36b147e2adc0ab8bb6e8cccbe4bd1f510de7fdc04e42 10529 libreswan_3.22-4_amd64.buildinfo Files: 0d4110d3e42acb310c8a34856c0d5e5c 2568 net optional libreswan_3.22-4.dsc 12234383b331ca54011dcfe9aa96271e 16412 net optional libreswan_3.22-4.debian.tar.xz 680f6292bbb97383f8499b36f2fe5118 10529 net optional libreswan_3.22-4_amd64.buildinfo -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEzicvlOwymaWlnoHjyu+ogyFnUzMFAlpWR5QACgkQyu+ogyFn UzNYyQ/8DhaeTMcZD0XN/2f89mcjqfYSldNyzhFuR878+S1IPVYA6MpcU1WIBGDK MjcI8pEhjCzoS+YIkFfSI7wOEG+ECGkDsSp0fZs0UFovgnWg8DjE842GK6HEx/el TC4BzqtFH1cpE69UKjz1s3UuSpQ6ouAjtE7LxSBYuabNtkRNyL0xE6OBHmcj+Hb7 c8tULNqYUcp7ekVd3+wA3n4tMHGt4J5mQHbOoowdfYXBbOosK6F9YhpbFE6ciA8/ AKMiwpx7lfHXjEs6JhfhkENhoRIh1ZUqJvv1GHZS63GQm+OVIDFqbQ+R/UFQzVjz XpMXBIWgbI+/s0xoETc4RQ8/GZh7TpCBHq+eSLxc0WH/Ev4/+qZkfICUuCyYzQh1 kVxRYHEmhgvcnAUMhYP/TmYmn3xGADtsTROIEfwoX7SBZDfAftf3LQQWrO+2DZEw W6JMw1ndRK8FMRgmfZGkX39C7TWbKFE8oIcI8LdfZ7RREOsOlp8XmLW81FWu5lgA gs+XD3tSHF7X6CO66Gm2E2JSYu+1Wr5V9RiPQi459PGmmfryEGM1V0T104gnq9Fz 0jSq7EY+QWdTbYRslvlF7A51QYOnuFKlAgN8bQCxWjPodeRRoC/xI+iViRDr9an6 Wqetlt+7go/IOsZaLcFt4a86UqTBuRl22FTrgCYbyXlNRvgG8Cc= =52O2 -----END PGP SIGNATURE-----
--- End Message ---