FS#68830 - [systemd] systemd v247 ships two systemd-user pam files
Attached to Project:
Arch Linux
Opened by AMM (amish) - Thursday, 03 December 2020, 01:53 GMT
Last edited by Buggy McBugFace (bugbot) - Saturday, 25 November 2023, 20:14 GMT
Opened by AMM (amish) - Thursday, 03 December 2020, 01:53 GMT
Last edited by Buggy McBugFace (bugbot) - Saturday, 25 November 2023, 20:14 GMT
|
Details
Description:
Since systemd v247 Arch linux ships two versions of systemd-user PAM file. /usr/lib/pam.d/systemd-user /etc/pam.d/systemd-user This is due to systemd moving their PAM file to /usr/lib/pam.d Systemd also recommends that vendors migrate to /usr/lib/pam.d from /etc/pam.d https://github.com/systemd/systemd/blob/master/NEWS#L122 > We recommend moving all packages' vendor versions of their > PAM stack definitions from /etc/pam.d/ to /usr/lib/pam.d/, > but if such OS-wide migration is not desired the location to > which systemd installs its PAM stack configuration may be > changed via the -Dpamconfdir Meson option. Because of presence of /etc/pam.d/systemd-user the /usr/lib/pam.d/systemd-user is never used by PAM library. (So only one is required) We need to decided which version is best and move it to /usr/lib/pam.d/ PS: There is also an old and related discussion / bug report here. (regarding PAM directory) https://bugs.archlinux.org/task/61790 Additional info: * package version(s) systemd 247 * config and/or log files etc. /usr/lib/pam.d/systemd-user /etc/pam.d/systemd-user * link to upstream bug report, if any https://github.com/systemd/systemd/blob/master/NEWS#L122 |
This task depends upon
Closed by Buggy McBugFace (bugbot)
Saturday, 25 November 2023, 20:14 GMT
Reason for closing: Moved
Additional comments about closing: https://gitlab.archlinux.org/archlinux/p ackaging/packages/systemd/issues/5
Saturday, 25 November 2023, 20:14 GMT
Reason for closing: Moved
Additional comments about closing: https://gitlab.archlinux.org/archlinux/p ackaging/packages/systemd/issues/5
FS#52039.https://github.com/systemd/systemd/blob/v247/NEWS#L122
Fix is easy - in PKGBUILD:
# overwrite the systemd-user PAM configuration with our own
-install -D -m0644 systemd-user.pam "$pkgdir"/etc/pam.d/systemd-user
+install -D -m0644 systemd-user.pam "$pkgdir"/usr/lib/pam.d/systemd-user