Your message dated Tue, 06 Feb 2024 17:08:03 +0000
with message-id <e1rxovt-00glng...@fasolo.debian.org>
and subject line Bug#1062802: fixed in pam 1.5.3-3
has caused the Debian Bug report #1062802,
regarding libpam0t64: file loss during upgrade due to /usr-move DEP17
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.)


-- 
1062802: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062802
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libpam0t64
Version: 1.5.3-2
Severity: serious
Tags: patch
Control: affects -1 + libpam0g
User: helm...@debian.org
Usertags: dep17p1

Hi Steve,

pam also runs in to /usr-move breakage. This one looks fairly straight
forward. I'm attaching a patch to avoid interfering with the time64
transition. As with others, the diversions shall be removed in forky.

Helmut
diff --minimal -Nru pam-1.5.3/debian/changelog pam-1.5.3/debian/changelog
--- pam-1.5.3/debian/changelog  2024-02-02 19:27:45.000000000 +0100
+++ pam-1.5.3/debian/changelog  2024-02-03 12:18:52.000000000 +0100
@@ -1,3 +1,10 @@
+pam (1.5.3-2.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Mitigate /usr-move file loss. (Closes: #-1)
+
+ -- Helmut Grohne <hel...@subdivi.de>  Sat, 03 Feb 2024 12:18:52 +0100
+
 pam (1.5.3-2) experimental; urgency=medium
 
   * New Swedish Translations, Thanks Martin Bagge / brother, Closes: #1057775
diff --minimal -Nru pam-1.5.3/debian/clean pam-1.5.3/debian/clean
--- pam-1.5.3/debian/clean      2023-09-15 19:17:35.000000000 +0200
+++ pam-1.5.3/debian/clean      2024-02-03 12:17:11.000000000 +0100
@@ -1 +1,3 @@
 debian/local/pam_getenv.8
+debian/libpam0t64.preinst
+debian/libpam0t64.postrm
diff --minimal -Nru pam-1.5.3/debian/libpam0t64.postrm.in 
pam-1.5.3/debian/libpam0t64.postrm.in
--- pam-1.5.3/debian/libpam0t64.postrm.in       1970-01-01 01:00:00.000000000 
+0100
+++ pam-1.5.3/debian/libpam0t64.postrm.in       2024-02-03 12:18:52.000000000 
+0100
@@ -0,0 +1,13 @@
+#!/bin/sh
+
+set -e
+
+if [ "$1" = remove ]; then
+       for file in libpam.so.0 libpam.so.0.85.1 libpam_misc.so.0 
libpam_misc.so.0.82.1 libpamc.so.0 libpamc.so.0.82.1; do
+               dpkg-divert --package libpam0t64 --no-rename --remove --divert 
"/lib/#DEB_HOST_MULTIARCH#/$file.usr-is-merged" 
"/lib/#DEB_HOST_MULTIARCH#/$file"
+       done
+fi
+
+#DEBHELPER#
+
+exit 0
diff --minimal -Nru pam-1.5.3/debian/libpam0t64.preinst.in 
pam-1.5.3/debian/libpam0t64.preinst.in
--- pam-1.5.3/debian/libpam0t64.preinst.in      1970-01-01 01:00:00.000000000 
+0100
+++ pam-1.5.3/debian/libpam0t64.preinst.in      2024-02-03 12:18:52.000000000 
+0100
@@ -0,0 +1,13 @@
+#!/bin/sh
+
+set -e
+
+if [ "$1" = install ]; then
+       for file in libpam.so.0 libpam.so.0.85.1 libpam_misc.so.0 
libpam_misc.so.0.82.1 libpamc.so.0 libpamc.so.0.82.1; do
+               dpkg-divert --package libpam0t64 --no-rename --add --divert 
"/lib/#DEB_HOST_MULTIARCH#/$file.usr-is-merged" 
"/lib/#DEB_HOST_MULTIARCH#/$file"
+       done
+fi
+
+#DEBHELPER#
+
+exit 0
diff --minimal -Nru pam-1.5.3/debian/rules pam-1.5.3/debian/rules
--- pam-1.5.3/debian/rules      2024-01-15 23:58:49.000000000 +0100
+++ pam-1.5.3/debian/rules      2024-02-03 12:18:50.000000000 +0100
@@ -76,3 +76,8 @@
 
 override_dh_installchangelogs:
        dh_installchangelogs NEWS
+
+debian/%:debian/%.in
+       sed -e 's/#DEB_HOST_MULTIARCH#/$(DEB_HOST_MULTIARCH)/g' $< > $@
+
+execute_before_dh_installdeb:debian/libpam0t64.preinst debian/libpam0t64.postrm

--- End Message ---
--- Begin Message ---
Source: pam
Source-Version: 1.5.3-3
Done: Helmut Grohne <hel...@subdivi.de>

We believe that the bug you reported is fixed in the latest version of
pam, 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 1062...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Helmut Grohne <hel...@subdivi.de> (supplier of updated pam 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: SHA256

Format: 1.8
Date: Sat, 03 Feb 2024 12:18:52 +0100
Source: pam
Architecture: source
Version: 1.5.3-3
Distribution: experimental
Urgency: medium
Maintainer: Sam Hartman <hartm...@debian.org>
Changed-By: Helmut Grohne <hel...@subdivi.de>
Closes: 1062802
Changes:
 pam (1.5.3-3) experimental; urgency=medium
 .
   [ Helmut Grohne ]
   * Mitigate /usr-move file loss. (Closes: #1062802)
Checksums-Sha1:
 ecc96a44cf8fb0237c03d38cf3378f515e941525 2154 pam_1.5.3-3.dsc
 ebc09cde9b98b075777956893396e4d1d2b870e7 139884 pam_1.5.3-3.debian.tar.xz
 4774c34445d6d6a54cc6729e2c392146dc12f72b 5391 pam_1.5.3-3_source.buildinfo
Checksums-Sha256:
 e3b5f1e1e02384a69f268e98da215094d5d0bba63b1ec6a90f314e341a240b16 2154 
pam_1.5.3-3.dsc
 e79a84364bff13679bbc7fa49ec4eeb0ea8d8b17ae3259feedf9afa3a2b9d22b 139884 
pam_1.5.3-3.debian.tar.xz
 54413feaf9ae11e96f325e5b49f69fe632997b745dfa0b8e55108c4011bbda5d 5391 
pam_1.5.3-3_source.buildinfo
Files:
 192162b09d40d3e7ea3b328b1834f1b5 2154 libs optional pam_1.5.3-3.dsc
 51e2d073e7ae2c11aec63f9251ddadfa 139884 libs optional pam_1.5.3-3.debian.tar.xz
 716efb23eb98bd2349de58236bfe5903 5391 libs optional 
pam_1.5.3-3_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iHUEARYIAB0WIQSj2jRwbAdKzGY/4uAsbEw8qDeGdAUCZcJengAKCRAsbEw8qDeG
dH3hAQDsuXQnUDgkWmUCYD8Wm6qCei/Hhv788qACesQBTu9C1wEApXxmCfwKvG59
lOt5m9/4UNn95cE6n12JYSomVZq2tA0=
=4CWL
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to