... >>> Merging sys-libs/pam-0.99.8.0-r1 to / * * Your current setup is using one or more of the following modules, * that are not built or supported anymore: * pam_pwdb, pam_radius, pam_timestamp, pam_chroot * If you are in real need for these modules, please contact the maintainers * of PAM through http://bugs.gentoo.org/ providing information about its * use cases. Note: The repository at /usr/local/portage does not have a profiles/repo_name entry. This can reduce the functionality of the repository in some cases. Note: The repository at /usr/portage/local/layman/sunrise does not have a profiles/repo_name entry. This can reduce the functionality of the repository in some cases. * * ERROR: sys-libs/pam-0.99.8.0-r1 failed. * Call stack: * ebuild.sh, line 1663: Called dyn_preinst * ebuild.sh, line 1100: Called pkg_preinst * pam-0.99.8.0-r1.ebuild, line 168: Called die * * deprecated PAM modules still used * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/portage/sys-libs/pam-0.99.8.0-r1/temp/build.log'. * !!! FAILED preinst: 1 * Messages for package sys-libs/pam-0.99.8.0-r1: * * Your current setup is using one or more of the following modules, * that are not built or supported anymore: * pam_pwdb, pam_radius, pam_timestamp, pam_chroot * If you are in real need for these modules, please contact the maintainers * of PAM through http://bugs.gentoo.org/ providing information about its * use cases. * * Your current setup is using one or more of the following modules, * that are not built or supported anymore: * pam_pwdb, pam_radius, pam_timestamp, pam_chroot * If you are in real need for these modules, please contact the maintainers * of PAM through http://bugs.gentoo.org/ providing information about its * use cases. * * ERROR: sys-libs/pam-0.99.8.0-r1 failed. * Call stack: * ebuild.sh, line 1663: Called dyn_preinst * ebuild.sh, line 1100: Called pkg_preinst * pam-0.99.8.0-r1.ebuild, line 168: Called die * * deprecated PAM modules still used ... # find /etc/pam.d/ -type f | xargs grep pam_pwdb /etc/pam.d/diald:auth required pam_pwdb.so shadow /etc/pam.d/diald:account required pam_pwdb.so #
Modify your /etc/pam.d/diald as follows and tell me if it works for ya: #%PAM-1.0 auth include system-auth auth required pam_nologin.so account include system-auth P.S.: When I say 'works', I'm referring to diald, not to pam-0.99 emerging.
(In reply to comment #1) > Modify your /etc/pam.d/diald as follows and tell me if it works for ya: > #%PAM-1.0 > auth include system-auth > auth required pam_nologin.so > account include system-auth Alin, the order is wrong; nologin will be ignored unless moved above system-auth.
Chances are you don't use pam with diald, therefore I've fixed it in -r2 without waiting for your confirmation. x86 team, can you mark the new revision stable? Changes are the following: - install a safe default for /etc/pam.d/diald - add pam USE flag; when is disabled, nopam.patch is applied - sanitize dependencies - remove src_compile() (the default implementation of this function works just as well)
x86 stable and closing
So I have 1.0-r2 installed now with the default pam.d/ file but cannot comment more on that. I have it installed but actually never got to configure the thing. :(
