Synched today and updating world gives me this block: sys-apps/pam-login (is blocking sys-apps/shadow-4.0.14-r2) Seems like sys-apps/pam-login depends on sys-apps/shadow, but the later blocks sys-apps/pam-login -- sys-apps/pam-login-4.0.14.ebuild -- DEPEND="virtual/libc sys-libs/pam >=sys-apps/shadow-4.0.11.1-r1 skey? ( app-admin/skey ) selinux? ( sys-libs/libselinux )" -- -- sys-apps/shadow-4.0.14-r2.ebuild -- RDEPEND=">=sys-libs/cracklib-2.7-r3 pam? ( virtual/pam ) !sys-apps/pam-login skey? ( app-admin/skey ) selinux? ( >=sys-libs/libselinux-1.28 ) nls? ( virtual/libintl )" --
No, pam-login is now merged back into shadow package, so just unmerge pam-login and then update shadow.
*** This bug has been marked as a duplicate of 79606 ***
*** Bug 126290 has been marked as a duplicate of this bug. ***
*** Bug 126610 has been marked as a duplicate of this bug. ***
(In reply to comment #1) > No, pam-login is now merged back into shadow package, so just unmerge pam-login > and then update shadow. > This worked for me.
*** Bug 128276 has been marked as a duplicate of this bug. ***
*** Bug 134958 has been marked as a duplicate of this bug. ***
*** Bug 135022 has been marked as a duplicate of this bug. ***
*** Bug 135025 has been marked as a duplicate of this bug. ***
*** Bug 135059 has been marked as a duplicate of this bug. ***
Shouldn't there be a away to inform users about that kind of changes? For example have pam-login-9999 that does not install anything but only print a message to the user to unmerge pam-login since the shadow package replaces it?
*** Bug 135170 has been marked as a duplicate of this bug. ***
*** Bug 135240 has been marked as a duplicate of this bug. ***
*** Bug 135299 has been marked as a duplicate of this bug. ***
*** Bug 135311 has been marked as a duplicate of this bug. ***
*** Bug 135335 has been marked as a duplicate of this bug. ***
*** Bug 135334 has been marked as a duplicate of this bug. ***
*** Bug 140741 has been marked as a duplicate of this bug. ***
*** Bug 141011 has been marked as a duplicate of this bug. ***
*** Bug 144039 has been marked as a duplicate of this bug. ***