Package: libpam-runtime Version: 1.3.1-5 Severity: normal X-Debbugs-Cc: j...@joshtriplett.org
As part of an mmdebstrap chroot creation for an embedded application that will never have any interactive users or logins, I tried to purge the libpam-runtime package (dpkg --force-remove-essential --force-depends --purge libpam-runtime). This resulted in the following: Removing libpam-runtime (1.3.1-5) ... PAM configuration ----------------- No PAM profiles have been selected. No PAM profiles have been selected for use on this system. This would grant all users access without authenticating, and is not allowed. Please select at least one PAM profile from the available list. No PAM profiles have been selected. No PAM profiles have been selected for use on this system. This would grant all users access without authenticating, and is not allowed. Please select at least one PAM profile from the available list. No PAM profiles have been selected. ... It loops at this point, producing output continuously. I realize that this is an essential package, but it does have a prerm and postrm script, and on a system with absolutely no usage of PAM it should be posible to remove without encountering an infinite loop like this. I can reliably reproduce this. -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.9.0-4-amd64 (SMP w/4 CPU threads) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libpam-runtime depends on: ii debconf [debconf-2.0] 1.5.74 ii libpam-modules 1.3.1-5 libpam-runtime recommends no packages. libpam-runtime suggests no packages. -- debconf information excluded
