Package: libpam0g
Version: 1.4.0-9
Severity: important
Tags: d-i
X-Debbugs-Cc: rklas...@communitascare.com
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of this action?
* What outcome did you expect instead?
*** End of the template - remove these template lines ***
-- System Information:
Debian Release: 11.0
APT prefers stable-security
APT policy: (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-8-amd64 (SMP w/32 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages libpam0g depends on:
ii debconf [debconf-2.0] 1.5.77
ii libaudit1 1:3.0-2
ii libc6 2.31-13
libpam0g recommends no packages.
Versions of packages libpam0g suggests:
pn libpam-doc
-- debconf information:
libpam0g/xdm-needs-restart:
libpam0g/restart-failed:
* libraries/restart-without-asking: true
libpam0g/restart-services:
On upgrading from buster to bullseye, libpam09 postinst script insisted on
restarting a number of services, but failed on the two services (hylafax and
exim)
that had no systemd units but were rather started and stopped via systemd's
sysv compatibility function.
This halted the upgrade and left the server in a semi-crippled state. I was
only able to continue the upgrade
by extracting the deb and removing references to hylafax and exim from the
postinst script.
