The subject says it all: In the ebuild, --libdir=/usr/$(get_libdir) is hardcoded, while it is '$(prefix)'/$(get_libdir) in 1.3.0-r2. This leads to plugins being installed in /usr/lib64/security instead of /lib64/security with version 1.3.0-r2, and system breakage. It may be that there is an error in the previous version ($prefix isn't actually set in multilib_src_configure), but the consequence was correct since all other ebuilds including systemd install to /lib64/security. Thanks and best regards, Bernd
please write the full package name in the summary. There are many pam packages.
The full package name is sys-libs/pam-1.3.1. The bad ebuild was introduced by this commit: commit 42bd1f101e777d779dd4b740a0a7f2bbe41a1432 Author: Mikle Kolyada <zlogene@gentoo.org> Date: Tue Oct 2 01:20:22 2018 +0300 sys-libs/pam: Version bump (v1.3.1) and later fixed by this commit: commit 5922f2cc41fd354eea0a8b632fef55fbb48db228 Author: Mikle Kolyada <zlogene@gentoo.org> Date: Tue Oct 2 10:46:52 2018 +0300 sys-libs/pam: add missing enable-securedir option However, the revision number was not bumped by the fix, so anyone who fetched the portage tree between those commits and built pam from it will be stuck with the broken version (until they manually rebuild it).
(In reply to Torbjörn Lönnemark from comment #2) > The full package name is sys-libs/pam-1.3.1. > > The bad ebuild was introduced by this commit: > > commit 42bd1f101e777d779dd4b740a0a7f2bbe41a1432 > Author: Mikle Kolyada <zlogene@gentoo.org> > Date: Tue Oct 2 01:20:22 2018 +0300 > > sys-libs/pam: Version bump (v1.3.1) > > > and later fixed by this commit: > > commit 5922f2cc41fd354eea0a8b632fef55fbb48db228 > Author: Mikle Kolyada <zlogene@gentoo.org> > Date: Tue Oct 2 10:46:52 2018 +0300 > > sys-libs/pam: add missing enable-securedir option > > > However, the revision number was not bumped by the fix, so anyone who > fetched the portage tree between those commits and built pam from it will be > stuck with the broken version (until they manually rebuild it). ... or those who used the daily snapshot / patches like I did ... Thanks for the explanation, I see it is now fixed and will be fixed in tomorrow's snapshot...
