Bug#983183: Aw: Bug#983183: Acknowledgement (libpam-script: Wrong path for pam_script.so)

Dear Martijn, as I saw at TDO libpam-script is now marked for autoremoval. This is the last thing I intended and the proper solution seems obvious to me.   Is there anything I can do to keep libpam-script in Debian 11?   Thanks a lot Christian Meyer  

Bug#983183: libpam-script: Wrong path for pam_script.so

ails of PAM and pam_script, but I think simply moving the directory should be the right solution. Please fix it in the remaining bullseye-freeze. Thank you Christian Meyer -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Ar

Bug#836635: libpam-mount: please drop the build dependency on hardening-wrapper

ould be able to stay in Debian. Christian Meyer

Bug#605662: upgrade-reports: removing splashy prevents booting (#512951)

fixed in lenny, too. Workaround: booting via live CD and renaming /etc/lsb-base-logging.sh manually. After that, splashy is still called during startup (initrd?) and causes a "splashy: 'command not found'" IIRC, but that is less important. Please adress this, too. Thanks

Bug#546711: Missleading dialogue text

worse). Please change the message text to something like "What do you want to happen to the conffile /etc/default/grub" or at least otherwise make clear that debconf means the conffile and not the whole package. Christian Meyer __