I haven't found this reported here yet while searching for "pam-login" and "shadow". My portage tree was sync'ed from europe a while ago, forgive me if it's already fixed. (? - If it IS a bug...) [blocks B ] sys-apps/pam-login (is blocking sys-apps/shadow-4.0.14-r2) [ebuild R ] sys-apps/shadow-4.0.14-r2 USE="nls pam -nousuid -skey" 0 kB I think that the ebuild for shadow 4.0.14-r2 should be like r1 in line 21: r2 RDEPEND: RDEPEND=">=sys-libs/cracklib-2.7-r3 pam? ( virtual/pam ) !sys-apps/pam-login ##################### ########LINE 21 skey? ( app-admin/skey ) selinux? ( >=sys-libs/libselinux-1.28 ) nls? ( virtual/libintl )" r1 RDEPEND: RDEPEND=">=sys-libs/cracklib-2.7-r3 pam? ( virtual/pam ) !pam? ( !sys-apps/pam-login )##################### LINE 21 skey? ( app-admin/skey ) selinux? ( >=sys-libs/libselinux-1.28 )"
*** This bug has been marked as a duplicate of 126014 ***
As far as I can see, sys-apps/pam-login functionality is embedded in sys-apps/shadow-4.0.14-r2 which makes sys-apps/pam-login redundant. You should just unmerge pam-login before updating to shadow-4.0.14-r2.