Your message dated Tue, 07 Nov 2023 15:35:15 +0000 with message-id <e1r0o6l-00h0eq...@fasolo.debian.org> and subject line Bug#1055485: fixed in systemd 255~rc1-3 has caused the Debian Bug report #1055485, regarding libpam-systemd needs a versioned conflict for libpam-elogind-compat 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.) -- 1055485: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055485 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: libpam-elogind-compat Version: 1.3 Severity: serious Justification: silent file overwrite in upgrade situation User: helm...@debian.org Usertags: dep17p1 Control: clone -1 -2 Control: affects -1 + libpam-systemd Control: retitle -2 libpam-systemd needs a versioned conflict for libpam-elogind-compat Control: reassign -2 libpam-systemd Control: found -2 255~rc1-2 Control: affects -2 + libpam-elogind-compat Control: block -2 by -1 libpam-elogind-compat declares "Replaces: libpam-systemd", because they both install e.g. /lib/x86_64-linux-gnu/security/pam_systemd.so on amd64. Since libpam-systemd/255~rc1-2 in experimental, this file is located in the corresponding location below /usr. Therefore the Replaces declaration is not matched by dpkg and becomes ineffective. The resulting behaviour is as if there was no replaces. This is problem class is described in more detail in DEP17[1] P1. The simplest mitigation for this kind of problem is preventing concurrent unpack by upgrading Replaces to Conflicts (and thus dropping the now implied Breaks). This mitigation is described in more detail in DEP17[1] M7. Do you know why Breaks+Replaces has been chosen here? Do you see any issues with upgrading to Conflicts? A timely solution is appreciated, because libpam-systemd will need a versioned Conflicts on unfixed versions of libpam-elogind-compat to avoid breaking upgrades. Helmut [1] https://subdivi.de/~helmut/dep17.html
--- End Message ---
--- Begin Message ---Source: systemd Source-Version: 255~rc1-3 Done: Luca Boccassi <bl...@debian.org> We believe that the bug you reported is fixed in the latest version of systemd, 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 1055...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Luca Boccassi <bl...@debian.org> (supplier of updated systemd 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: Tue, 07 Nov 2023 15:17:12 +0000 Source: systemd Architecture: source Version: 255~rc1-3 Distribution: experimental Urgency: medium Maintainer: Debian systemd Maintainers <pkg-systemd-maintain...@lists.alioth.debian.org> Changed-By: Luca Boccassi <bl...@debian.org> Closes: 1055485 Changes: systemd (255~rc1-3) experimental; urgency=medium . * Do not ship repart.standalone and shutdown.standalone * /usr/lib/sysvinit/telinit was dropped long ago, use /usr/sbin/telinit * Add Suggests: libip4tc2 as it is now dlopen'ed * Drop rc/rcS masking, no longer necessary * Add Conflicts to avoid issues due to DEP17P3. libpam-elogind-compat, opensysusers, bfh-container, molly-guard, and progress-linux-container divert files from our packages, so DEP17P3 is triggered. Add unversioned conflicts until those diversions are updated according to DEP17M18, and then we can make the conflicts versioned. (Closes: #1055485) Checksums-Sha1: 75f97dc0f8bf03e154af9c8b447ccd72e6958888 6897 systemd_255~rc1-3.dsc 8ec874a656a8313bdbf32fdc8d11afc70510a343 163436 systemd_255~rc1-3.debian.tar.xz 6501dc35c91cda867959b7bba085b98501303a00 12404 systemd_255~rc1-3_source.buildinfo Checksums-Sha256: 35c45347f479ba4861e04912d87e99f81427b1ba35c0f20cf57dd0934382f9ab 6897 systemd_255~rc1-3.dsc bbb4d67a391c3ad706120e9c769a8dd0ba931dd0c869395e5d7fc245f3214e49 163436 systemd_255~rc1-3.debian.tar.xz 2cbb0aba1e0b1a7ad7a6b8d1621582dba5976b622dadad2d8aea0bae46db69bd 12404 systemd_255~rc1-3_source.buildinfo Files: 87181a3f0a97e9bbd998ac406d8314a5 6897 admin optional systemd_255~rc1-3.dsc 6ab75b486c63811006a9092605cb51dd 163436 admin optional systemd_255~rc1-3.debian.tar.xz 573c290a4f568bca46dc9e90fb730e13 12404 admin optional systemd_255~rc1-3_source.buildinfo -----BEGIN PGP SIGNATURE----- iQJFBAEBCgAvFiEErCSqx93EIPGOymuRKGv37813JB4FAmVKVV4RHGJsdWNhQGRl Ymlhbi5vcmcACgkQKGv37813JB7JPg//eZrDYk4/pLKBCoTNEf0HtVTogjJXMKYj o8EwKdYUNxOL124JfPXUxrWYyqF+AgfC8R2QKjWOBUbUK26gHMn8d+FP9+e0fZI7 9kW+2+NlUS2gpdT0esEKJHSnD62Ap1XRa0e7Lfmjqs8/cx3sbluLlyflWdWmC4nM c0/5xfb4v2DazsGmAj67+rbln868RDWQRcDi1XhPiVPxm1o+KYBWB8JPrWo4dtkv oEKgen1BI+s/J0eUD6Vr7SggiA0PV64WhxccxjSGwVW21XrudAsQcCM3dSLxIGCM nzoh4Ts++Pbmg584Sd7AjgZIMKW/nVF9dcp/cMDaiAT3r/pFB+wsjCNp81cc8o/t 0jqy61+jyYF4Ku7Iotrotb8ofbqMgcV7a6TI2wOhRrI+9EIHzZRptZHp4WeR5zhy RRqLMhcK4+OrnfKquOmeE+HNP1w//iJ9cCf5ekpegK/fqAMvkDd8qxtEtz/rspbR m/pPqrAypXjBKyV6owHbA4AH8uF2fuzw6tuphpS7lavJb+dkZkKiqmzsxtC9W4wC UUSUcFxxIKWvwdkT9G3EyxZ/dQOFAIdZm3fy4iiM/E6sOg8dQ1glSk9Dk6k1YNpS 4saTOKNPF/idQYXkuoWUhAyuVUY3PudnV5tDx9qpGrojQz0HlLqP+WFPOtzrT9ie 5r8iSdYUc/Y= =xB1E -----END PGP SIGNATURE-----
--- End Message ---
