Your message dated Wed, 15 Nov 2023 19:09:34 +0000 with message-id <e1r3lgy-004wzp...@fasolo.debian.org> and subject line Bug#1055485: fixed in systemd 255~rc2-1 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~rc2-1 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: Wed, 15 Nov 2023 17:10:26 +0000 Source: systemd Architecture: source Version: 255~rc2-1 Distribution: unstable Urgency: medium Maintainer: Debian systemd Maintainers <pkg-systemd-maintain...@lists.alioth.debian.org> Changed-By: Luca Boccassi <bl...@debian.org> Closes: 1053301 1055485 1055863 Changes: systemd (255~rc2-1) unstable; urgency=medium . [ Matthias Geiger ] * Bump version number for udev.postinst and udev.maintscript * Fix udev.postinst to preserve the enablement of the init script. When transferring ownership of the udev init script to sysvinit, the service was disabled as it didn't check for enablement before calling update-rc.d. Thanks to Mark Hindley for the original fix. (Closes: #1053301) . [ Luca Boccassi ] * New upstream version 255~rc2 * Drop fix-build-without-SBAT_DISTRO.patch, merged upstream * Refresh patches * Upload to unstable . systemd (255~rc1-4) experimental; urgency=medium . * Add version to Conflict with molly-guard * Move systemd-hwdb-update.service to udev package. Commit a12cf5d187cb in 249-1 removed systemd-hwdb-update.service from udev, and 254.4-1 re-added it in systemd, so move it back to udev. (Closes: #1055863) . 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) . systemd (255~rc1-2) experimental; urgency=medium . * Build-depend on python3-pefile on all architectures ukify * meson: use enabled/disabled instead of true/false for 'feature' options * meson: use canonical paths for configured tools too . systemd (255~rc1-1) experimental; urgency=medium . [ Michael Biebl ] * Update symbol versions for the final 254 release * Remove mangling of man pages post build trying to fix up paths. With merged-/usr being mandatory, this is no longer necessary as the paths will now always point to the correct location. * Use a drop-in to avoid startup failures of systemd-logind when dbus is missing. Instead of patching the systemd-logind.service file, use a drop-in. This way the Debian specific change becomes more visible and easier to override. . [ Luca Boccassi ] * New upstream version 255~rc1 * Drop test-skip-test-path-on-Salsa-CI.patch, merged upstream * Drop Move-sysusers.d-sysctl.d-binfmt.d-modules-load.d-back-to-.patch, no longer necessary * Refresh patches * Temporarily keep systemd.pc and udev.pc pointing to legacy unmerged paths. This will be dropped in the short term, but there are still a lot of FTBFS when changing, so keep it for now * systemd/udev: assert that the system is merged-usr. Support for unmerged system was dropped project-wide. Things will break subtly if ran on such unsupported setups, so add an explicit assert at preinst. * Drop deprecated split-usr and install files from /usr * Install new pam_systemd_loadkey module. If configured, and systemd- cryptsetup and logind are used, the crypsetup passphrase is passed to the PAM stack for later authentication steps such as the GNOME keyring. * Install the default pcrlock config files * Update libsystemd0.symbols * autopkgtest: add dependencies on python3-pefile and nvme-cli for upstream suite * Backport patch to fix arm64 cross-build * Update Lintian overrides Checksums-Sha1: 04257fa0cabf1eab53e0b0e85cf958f37e48d9d6 6897 systemd_255~rc2-1.dsc 465bcdf9123d22b816c31010b99a9b3d98faa31a 14844357 systemd_255~rc2.orig.tar.gz 166254fef6e2fb65e0e0321edaacda655f9677dd 163632 systemd_255~rc2-1.debian.tar.xz 49b7f692c65ed76586efccc296a0b3022d4c342c 12404 systemd_255~rc2-1_source.buildinfo Checksums-Sha256: c6ab939f666ad7ae29d62f434d8fd8b9089c57a228d630743a74580c37db289e 6897 systemd_255~rc2-1.dsc 56aa2f165a6b375ef51d13c8521d1530d9fb5a62b58e35d64b851c1a1b4cbaca 14844357 systemd_255~rc2.orig.tar.gz 2eadb6183234d7e366e05a22f96268849910d7b77fdf2dbf7fb43aa2447f30be 163632 systemd_255~rc2-1.debian.tar.xz 8d0c6fd1f3b43666da900d5b49b2d38946225f47dc63a3dcb59478952569dacd 12404 systemd_255~rc2-1_source.buildinfo Files: 517850020af02b04529646cd18c96ce4 6897 admin optional systemd_255~rc2-1.dsc a66d1fac64a1494f41c4e75399eb776b 14844357 admin optional systemd_255~rc2.orig.tar.gz 5cbb215e24a2dcaf9b627a09ce88b9a7 163632 admin optional systemd_255~rc2-1.debian.tar.xz da75b07e489a4a68cd51befb15903178 12404 admin optional systemd_255~rc2-1_source.buildinfo -----BEGIN PGP SIGNATURE----- iQJFBAEBCgAvFiEErCSqx93EIPGOymuRKGv37813JB4FAmVVETwRHGJsdWNhQGRl Ymlhbi5vcmcACgkQKGv37813JB47+xAAk7Wzu28B6Ydc0CGvs2HXeHFC0gzoya6D 6iJ+t8E6a/lczsdT3em3EnCOG6Gz23WjLwRWrY/0EjSFACqt4/D5MklBMFjh/1g1 M03MZVyuX5rkF0pQ2XluTWp1PqiqYa7/Q7GioxJNYSj52rNyswsFT9fxOZ0hJWDt pfb2jZpNIXc+lr0RsRxI9X7KEGL0Z95KGFWf8fHHukESxdWQX+PzrRkBwkxdadt9 SmoYSrBW64bnjW70ZolLxdVw7TAGr/P3ca8Wd7aBhqJuZUYvvZO2oWf00+4W5q4B /5XylcfCeXaZyAKP+YjDeJH27pKE01BuS4YGXAkt50TBg5ru8tyq0dGgLHBXfiPn p7XkdhswQho1TFadpe1/vBwPirSpjsmOOubgtCFVgE8nDVAUdbH1OGWoooGCbjaL d0ygmDaTs3pdbSryFejTRyO6eVv2IBu6WulbHHZoHBgNBDvC1kLDpjR03+89KMfP y+bwB1UAeklLTpg0W+5rajXWEb4WC7dP0o+CT+SVp5jvMpjfY33QrByEypsARnOa SUl2um0lB+z0PgM2jgzZbS6XhbBs0JDStVpMuAORIGYhPw9etWmWaG+9rezJqMnh YmtKDV/qfEsEP7xpShBIWsAGobdbknEguzgmBVpiBI/L2klvgqEQujVMT6ZMz+Y0 7wypzyLElsI= =m02j -----END PGP SIGNATURE-----
--- End Message ---
