Hi Disclaimer, not the maintainer here, but maintainer of a package which would get autoremoved.
On Sat, Aug 05, 2023 at 02:17:53PM +0200, Andreas Beckmann wrote: > 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. AFAICS, libesmtp5 is very long gone already from Debian, and the check you are doing is from stretch to weeezy, as well for a very long time obsoleted now. Usually one would drop constraints which are not anymore relevant for suites in Debian, so I wonder if we here not simply can drop the Replaces relation which is irrelevant in any supported suites. Regards, Salvatore
