Bugzilla Bug 125419

shouldnt be any trouble here that i know of

shadow-4.0.14-r1 and pam-login-4.0.14 stable on ppc64

both stable on amd64

sparc'em.

Skey is installed, but can't seem to get shadow and/or pam-login to build with
skey support. 

emerge -pv shadow pam-login:
[ebuild   R   ] sys-apps/pam-login-4.0.14  USE="selinux skey -livecd -nls" 0 kB 
[ebuild   R   ] sys-apps/shadow-4.0.14-r1  USE="pam selinux skey -nls -nousuid"
0 kB 

But during the config phase I see:

shadow will be compiled with the followig feactures:

  auditing support:               yes
  CrackLib support:               yes
  PAM support:                    yes
  SELinux support:                yes
  shadow group support:           yes
  S/Key support:                  no

Am I overlooking something here?

you'll need to post config.log for me to figure out why that failed

configure option is --with-skey (not --with-libskey)

indeed ... seems that option changed somewhere along the line but no one
noticed before ... i'll update all the relevant versions, thanks for pointing
that out

x86 done \(^.^)/

ppc done.

It seems that on AMD64 there is a problem concerning shadow and pam-login:

Calculating world dependencies... done!

[blocks B     ] sys-apps/pam-login (is blocking sys-apps/shadow-4.0.14-r2)
!!! Error: The above package list contains packages which cannot be installed
!!!        at the same time on the same system.

That is on a full ~AMD64 system, with pam-login-4.0.14 installed

(In reply to comment #10)
> It seems that on AMD64 there is a problem concerning shadow and pam-login:
> 
> Calculating world dependencies... done!
> 
> [blocks B     ] sys-apps/pam-login (is blocking sys-apps/shadow-4.0.14-r2)
> !!! Error: The above package list contains packages which cannot be installed
> !!!        at the same time on the same system.
> 
> That is on a full ~AMD64 system, with pam-login-4.0.14 installed
> 

Perhaps it would be a good idea to find out why blockages occur:
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=2&chap=1#doc_chap4

(In reply to comment #11)
> 
> Perhaps it would be a good idea to find out why blockages occur:
> http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=2&chap=1#doc_chap4
> 
I'm fullay aware why blockages occur, but I noted the problem here nevertheless
to prevent this problem occurring in a stable environment as well.

(In reply to comment #11)
>
> Perhaps it would be a good idea to find out why blockages occur:
> http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=2&chap=1#doc_chap4
> 
OK, I read that section, but it does't tell me how to find out which files are
conflicting.

It does suggest unemerging both packages and then emerging them both again. How
can that help? Won't that simply re-install the two compatible versions I
already have installed? Then I'm back in the same boat as I am now.

As an aside, I am extremely reluctant to remove something as important as
/bin/login or /bin/passwd. 

Is there a safe workaround?

If you read the changelog, shadow 4.0.14-r2 merges pam-login back inside a
single package.
So you just have to:

emerge -C pam-login
emerge -u shadow

and you'll have just the same you had before, but with a package less.
Full stop.

Alpha stable.

Both stable on mips.