Your message dated Thu, 29 Feb 2024 17:11:20 +0000
with message-id <e1rfjwg-00c6fb...@fasolo.debian.org>
and subject line Bug#1065017: fixed in pam 1.5.3-5
has caused the Debian Bug report #1065017,
regarding debootstrap: Fails for *sid* with `cannot move
/lib/x86_64-linux-gnu/libpam.so.0 as its destination exists as a symlink`
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.)
--
1065017: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065017
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debootstrap
Version: 1.0.134
Severity: normal
Dear Debian folks,
I am unable to bootstrap Debian sid/unstable. It worked some weeks ago.
$ sudo debootstrap --arch amd64 sid
/scratch/local2/pmenzel/debootstrap-test http://ftp.gwdg.de/debian/
W: Cannot check Release signature; keyring file not available
/usr/share/keyrings/debian-archive-keyring.gpg
I: Retrieving InRelease
I: Retrieving Packages
I: Validating Packages
I: Resolving dependencies of required packages...
I: Resolving dependencies of base packages...
I: Checking component main on http://ftp.gwdg.de/debian...
[…]
I: Retrieving libp11-kit0 0.25.3-4
I: Validating libp11-kit0 0.25.3-4
I: Retrieving libpam-modules 1.5.3-4
I: Validating libpam-modules 1.5.3-4
I: Retrieving libpam-modules-bin 1.5.3-4
I: Validating libpam-modules-bin 1.5.3-4
I: Retrieving libpam-runtime 1.5.3-4
I: Validating libpam-runtime 1.5.3-4
I: Retrieving libpam0g 1.5.2-9.1+b1
I: Validating libpam0g 1.5.2-9.1+b1
I: Retrieving libpam0t64 1.5.3-4
I: Validating libpam0t64 1.5.3-4
I: Retrieving libpcre2-8-0 10.42-4+b1
I: Validating libpcre2-8-0 10.42-4+b1
I: Retrieving libpopt0 1.19+dfsg-1+b1
I: Validating libpopt0 1.19+dfsg-1+b1
[…]
I: Extracting passwd...
I: Extracting perl-base...
I: Extracting sed...
I: Extracting sysvinit-utils...
I: Extracting tar...
I: Extracting tzdata...
I: Extracting usr-is-merged...
I: Extracting util-linux...
I: Extracting zlib1g...
E: cannot move /lib/x86_64-linux-gnu/libpam.so.0 as its destination
exists as a symlink
Kind regards,
Paul
--- End Message ---
--- Begin Message ---
Source: pam
Source-Version: 1.5.3-5
Done: Sam Hartman <hartm...@debian.org>
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 1065...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Sam Hartman <hartm...@debian.org> (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: Thu, 29 Feb 2024 09:46:54 -0700
Source: pam
Architecture: source
Version: 1.5.3-5
Distribution: unstable
Urgency: medium
Maintainer: Sam Hartman <hartm...@debian.org>
Changed-By: Sam Hartman <hartm...@debian.org>
Closes: 1065017
Changes:
pam (1.5.3-5) unstable; urgency=medium
.
* Revert renaming libpam0g to libpam0t64 for time_t transition: apt
sometimes removes libpam0g rather than simply letting libpam0t64
replace libpam0g (and deconfiguring libpam0g), leaving a system where
essential packages are broken, Closes: #1065017
* Since libpam0t64 is going away, we do not need dpkg-diversions for it.
* As a consequence libpam_misc has an ABI break without a package name
change. We believe nothing in the archive depends on this ABI, and at
least until we come up with a better solution this is the least bad option.
* For now remove libdb-dev so that libdb-dev can undergo time_t
transition. That means this version of pam does not include
pam_userdb, which makes pam unsuitable for release.
* Replace/break libpam0t64
Checksums-Sha1:
8c45da3949f350d00d6000ca7dbbc468b26bd30f 2238 pam_1.5.3-5.dsc
55121e5b670c27ff7f02a5cdf108bfe07decb391 139740 pam_1.5.3-5.debian.tar.xz
Checksums-Sha256:
8e0bcec3d45a68b3825be8daa4960f3318b31a1edb2db8253c8fc62f4969d3aa 2238
pam_1.5.3-5.dsc
d5fe6c66fa894c3738998a18029eafbf1d5aee121f68441b160f29f64e374c9b 139740
pam_1.5.3-5.debian.tar.xz
Files:
e9a89a9990b8c1eb43091f8d6fda033f 2238 libs optional pam_1.5.3-5.dsc
1760abb0660bc1d75024f2cf7cf3cc27 139740 libs optional pam_1.5.3-5.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iHQEARYIAB0WIQSj2jRwbAdKzGY/4uAsbEw8qDeGdAUCZeC18gAKCRAsbEw8qDeG
dHqTAQCH72iEE8pChlu0c48aebgr7879Odovevlz05+b+mBo1wD2KLaq4eBpZn8H
3As0iP7hUDzcIU9C5X6nxR+ryr41AA==
=jc3I
-----END PGP SIGNATURE-----
pgpvDbI4GiLdU.pgp
Description: PGP signature
--- End Message ---
