On Mon, Jun 15, 2026 at 12:57:03PM -0600, Sam Hartman wrote: > control: tags -1 patch > > >>>>> "Chris" == Chris Hofstaedtler <[email protected]> writes: > Chris> So what you are saying is that libpam0g's code for "include" > Chris> is broken, or at least inconsistent with the support for > Chris> /usr/lib/pam.d. > > I don't think pam in Debian cliams to (or does) support /usr/lib/pam.d. > So, I think that moving files there is broken.
Well, dh_installpam in debhelper compat 14 does now install the files into /usr/lib/pam.d. It's not that util-linux actively chose to do this. Without the patch, /usr/lib/pam.d DOES work; except as a source for include files. So, Debian's PAM does half-support it, courtesy of upstream. With the patch, the support would be at least more complete. > See https://lists.debian.org/[email protected] > for my rationale for not supporting /usr/lib/pam.d >From a really quick look at PAM earlier today, it seems PAM supports libeconf. Per my understanding of things, libeconf is what provides the support for "systemd-style" configs. Not sure how the integration looks like. If you don't want Debian to support /usr/lib/pam.d, then I think you should at least revert all upstream commits that try to support /usr/lib/pam.d; get dh_installpam to put the files into /etc/pam.d, and get these packages fixed: account-utils: /usr/lib/pam.d/{passwd,pwupd-chfn,pwupd-chsh,pwupd-passwd} libkscreenlocker6: /usr/lib/pam.d/{kde,kde-fingerprint,kde-smartcard} polkitd: /usr/lib/pam.d/polkit-1 systemd: /usr/lib/pam.d/systemd-user util-linux: /usr/lib/pam.d/{login,remote,runuser,runuser-l,su,su-l} A lintian error would also be in order. Chris
