Your message dated Mon, 21 Aug 2023 10:49:51 +0000 with message-id <e1qy2tn-006fwx...@fasolo.debian.org> and subject line Bug#1043058: fixed in libesmtp 1.1.0-3.1 has caused the Debian Bug report #1043058, regarding libesmtp6: missing Breaks: libesmtp5 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.) -- 1043058: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043058 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: libesmtp6 Version: 1.1.0-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts replaces-without-breaks Hi, during a test with piuparts and DOSE tools I noticed your package causes removal of files that also belong to another package. This is caused by using Replaces without corresponding Breaks. This leaves a crippled libesmtp5 package installed on certain upgrade paths. This is a serious bug violating policy 7.6, see https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces and also see the footnote that describes this incorrect behavior: https://www.debian.org/doc/debian-policy/ch-relationships.html#id13 The libesmtp6 package has the following relationships with libesmtp5: Conflicts: n/a Breaks: n/a Replaces: libesmtp5 >From the attached log (scroll to the bottom...): 3m29.5s ERROR: FAIL: debsums reports modifications inside the chroot: debsums: missing file /usr/lib/esmtp/sasl-cram-md5.so (from libesmtp5 package) debsums: missing file /usr/lib/esmtp/sasl-login.so (from libesmtp5 package) debsums: missing file /usr/lib/esmtp/sasl-plain.so (from libesmtp5 package) This wasn't noticed as long as libesmtp6 still provided the files, but that no longer seems to be the case. cheers, Andreas
libesmtp-dev_1.1.0-3+b1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---Source: libesmtp Source-Version: 1.1.0-3.1 Done: Salvatore Bonaccorso <car...@debian.org> We believe that the bug you reported is fixed in the latest version of libesmtp, 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 1043...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Salvatore Bonaccorso <car...@debian.org> (supplier of updated libesmtp 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, 19 Aug 2023 12:04:32 +0200 Source: libesmtp Architecture: source Version: 1.1.0-3.1 Distribution: unstable Urgency: medium Maintainer: Jeremy T. Bouse <jbo...@debian.org> Changed-By: Salvatore Bonaccorso <car...@debian.org> Closes: 1043058 Changes: libesmtp (1.1.0-3.1) unstable; urgency=medium . * Non-maintainer upload. * libesmtp6: Add versioned Replaces and Breaks against libesmtp5 (<< 1.0.6-1~) (Closes: #1043058) Checksums-Sha1: 9c2c76c6032698e88aec7ee72fee4e6755f3e876 2100 libesmtp_1.1.0-3.1.dsc 35ce434cd7bf269143118ead4d70e18213312d4f 4920 libesmtp_1.1.0-3.1.debian.tar.xz Checksums-Sha256: 1a54dded96b3cf809d075ab0869bb349adfa59db11f03a70915c8d26f69e1b76 2100 libesmtp_1.1.0-3.1.dsc 2aa53e59271970f0ad97dee72dd51fab28b2a49e4b3ceb58513c297c0109dbc9 4920 libesmtp_1.1.0-3.1.debian.tar.xz Files: 0d5c23728c2185b34de5ecb51934c98f 2100 libs optional libesmtp_1.1.0-3.1.dsc e134e04406f8fa73cb60fa7d3eaf9eeb 4920 libs optional libesmtp_1.1.0-3.1.debian.tar.xz -----BEGIN PGP SIGNATURE----- iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAmTglHNfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2 NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk ZWJpYW4ub3JnAAoJEAVMuPMTQ89EPgYP/0XQtyrPvJ5a2gy0QMO0RqDpEC9tkMwG pzwpDIp1hycXxBX7BAym/tE9rhOIBVoFKj4wrL+dqkzhoQvgQWnPZMPqort+jz14 ndAvaCV8aGmYPzSNuu/04onVTFunpEz5erIhe9moVX7+IkDCB6yKzmnETpNKJKDr QEa+zpt8CkvxbN9VyvAe9ZW7EwL+b3I/xV5a9jVs2BNWjJX9zgF/scz6vpWZ6xH6 yBI8MN+DcdWTc3OhRycGcPFAn0v88vu9eBvFCkVqn9oVA2BtbYr8tasNwDaXHyCV W9QyXrGfUl9qaFBlggDG8ZJMJG5yju+177mxNBe9GBQ1DUccyVGb/XefrfO6Qa5y OwZ+blFS67GwD+IvYT2VJmdFKuTror5tueJF+2ZWoI6srweVMtZ6OGKeUn95/OX0 y+kzFBd/0iuS8mJaCiU4u0TXgFh+T1mdTsVAa5jMoVtdE+Pn7wlBwoY7CWh9Fpvs djowaAXq1jWuHTRbWbGwDK3ovGmzMPprGmZvX0TDoyjb3sB6gO2KsxGm3LYaFzj4 tFfZYfNTXlEjEWEg7vG/joEmgMKv1mZvCWZpKpVsvXsYoaHcH9W32fiK/tepFtgA IlEL+uSqkFm0lFKVHcccRVzQ5QXaLX9q3F8UBrxWogjefqFgQgxJYC6Tul9HjwZB cbjpCKWHuhEd =31l1 -----END PGP SIGNATURE-----
--- End Message ---
