Bug 771132 – sys-libs/pam: chmod: cannot access '/build/lakitusbin/unix_chkpwd': No such file or directory

• Status: RESOLVED DUPLICATE of bug 771312
• Product: Gentoo Linux

[Description aaltinay101 2021-02-17 18:41:02 UTC]

* Messages for package sys-libs/pam-1.5.1 merged to /build/lakitu/:
 * Log file: /build/lakitu/tmp/portage/logs/sys-libs:pam-1.5.1:20210217-182938.log

 * FAILED postinst: 1
 * Some software with pre-loaded PAM libraries might experience
 * warnings or failures related to missing symbols and/or versions
 * after any update. While unfortunate this is a limit of the
 * implementation of PAM and the software, and it requires you to
 * restart the software manually after the update.
 * 
 * You can get a list of such software running a command like
 *   lsof / | egrep -i 'del.*libpam\.so'
 * 
 * Alternatively, simply reboot your system.
 * ERROR: sys-libs/pam-1.5.1::portage-stable failed (postinst phase):
 *   (no error message)


sbin/unix_chkpwd can't be found in my system.

Reproducible: Always

Steps to Reproduce:
1.emerge-lakitu pam
2.
3.

[Comment 1 Sam James 2021-02-17 18:49:55 UTC]

Please attach /build/lakitu/tmp/portage/logs/sys-libs:pam-1.5.1:20210217-182938.log and emerge --info from inside the new root too.

[Comment 2 aaltinay101 2021-02-17 19:28:25 UTC]

Created attachment 687321 [details]
emerge info

[Comment 3 aaltinay101 2021-02-17 19:28:51 UTC]

Created attachment 687324 [details]
pam logs

[Comment 4 Sam James 2021-02-17 19:43:43 UTC]

I don't really see how PAM makes sense in an EPREFIX, unless there's some case with --root or something I'm not considering.

Is there a reason we shouldn't just do nothing in a Prefix case..?

[Comment 5 aaltinay101 2021-02-17 22:44:25 UTC]

EPREFIX is not really necessary but we need to add "/".

[Comment 6 Mikle Kolyada (RETIRED) 2021-02-18 16:05:01 UTC]

prefix support in pam removed.

[Comment 7 Sam James 2021-02-18 19:29:08 UTC]

*** This bug has been marked as a duplicate of bug 771312 ***