Home | Docs | Forums | Lists | Bugs | Planet | Store | GMN | Get Gentoo!

Full Text Bug Listing

this bug is to help us track what needs to be done in order to get Gentoo to
work just fine without PAM

currently i know of these issues:
- PROVIDE be conditional via USE: Bug 32114
- install login.defs with shadow when USE=-pam: Bug 35405
- remove pam / pam-login from profiles/base/packages since `USE=pam emerge
shadow` would do the right thing

See also 69066

ok, all resolved now except for Bug 69066:

we need to:
 - create a virtual/login and put it into base/packages
 - remove pam / pam-login from base/packages
 - add a virtual/login in base/virtuals with pam-login as default provider

Hi!

Are there any updates on this matter? I'd really like PAM to be removed from my Gentoo. 

Thanks
Sebastian

we have to close sub bugs before we can close this one ;)

atm we need portage-2.0.51-r4 or better to be released

ok, for now, we have just shadow and pam-login that provide /bin/login

so rather than screwing around with virtual/login, i updated shadow-4.0.[56] like this:
DEPEND="
    pam? ( sys-libs/pam sys-apps/pam-login )
    !pam? ( !sys-apps/pam-login )
"

DEPEND="
    pam? ( sys-libs/pam sys-apps/pam-login )
    !pam? ( !sys-apps/pam-login )
"
the above condition was entered as
DEPEND="
    pam? ( sys-libs/pam sys-apps/pam-login )
    !pam? ( sys-apps/pam-login ) /* w/o additional ! */
"
and it pulls in pam-login for all cases (and pam-login depending on pam pulls 
pam also in)
uclibc killed
I can't disable RESOLVED FIXED, but it is not resolved fixed
All shadow versions stable and up are involved

Reopeing bug per comment #6
Attempting to verify.

Updating the ebuild to refelect 

Index: shadow-4.0.5-r2.ebuild
===================================================================
RCS file: /var/cvsroot/gentoo-x86/sys-apps/shadow/shadow-4.0.5-r2.ebuild,v
retrieving revision 1.4
diff -u -b -B -w -p -r1.4 shadow-4.0.5-r2.ebuild
--- shadow-4.0.5-r2.ebuild	24 Nov 2004 04:34:46 -0000	1.4
+++ shadow-4.0.5-r2.ebuild	25 Nov 2004 15:23:41 -0000
@@ -18,7 +18,7 @@ IUSE="pam selinux nls skey"
 
 RDEPEND=">=sys-libs/cracklib-2.7-r3
 	pam? ( >=sys-libs/pam-0.75-r4 sys-apps/pam-login )
-	!pam? ( sys-apps/pam-login )
+	!pam? ( !sys-apps/pam-login )
 	skey? ( app-admin/skey )
 	selinux? ( sys-libs/libselinux )"
 DEPEND="${DEPEND}
Index: shadow-4.0.5-r3.ebuild
===================================================================
RCS file: /var/cvsroot/gentoo-x86/sys-apps/shadow/shadow-4.0.5-r3.ebuild,v
retrieving revision 1.3
diff -u -b -B -w -p -r1.3 shadow-4.0.5-r3.ebuild
--- shadow-4.0.5-r3.ebuild	24 Nov 2004 04:34:46 -0000	1.3
+++ shadow-4.0.5-r3.ebuild	25 Nov 2004 15:23:42 -0000
@@ -18,7 +18,7 @@ IUSE="pam selinux nls skey"
 
 RDEPEND=">=sys-libs/cracklib-2.7-r3
 	pam? ( >=sys-libs/pam-0.75-r4 sys-apps/pam-login )
-	!pam? ( sys-apps/pam-login )
+	!pam? ( !sys-apps/pam-login )
 	skey? ( app-admin/skey )
 	selinux? ( sys-libs/libselinux )"
 DEPEND="${DEPEND}
Index: shadow-4.0.6.ebuild
===================================================================
RCS file: /var/cvsroot/gentoo-x86/sys-apps/shadow/shadow-4.0.6.ebuild,v
retrieving revision 1.3
diff -u -b -B -w -p -r1.3 shadow-4.0.6.ebuild
--- shadow-4.0.6.ebuild	24 Nov 2004 04:34:46 -0000	1.3
+++ shadow-4.0.6.ebuild	25 Nov 2004 15:23:42 -0000
@@ -18,7 +18,7 @@ IUSE="pam selinux nls skey"
 
 RDEPEND=">=sys-libs/cracklib-2.7-r3
 	pam? ( >=sys-libs/pam-0.75-r4 sys-apps/pam-login )
-	!pam? ( sys-apps/pam-login )
+	!pam? ( !sys-apps/pam-login )
 	skey? ( app-admin/skey )
 	selinux? ( sys-libs/libselinux )"
 DEPEND="${DEPEND}

InCVS
Looks good from native uclibc(-pam) and native glibc(+pam) envs.

changing resolution to FIXED

*** Bug 72411 has been marked as a duplicate of this bug. ***

Now we have:

shadow-4.0.x.ebuild: RDEPEND="... pam? ( >=sys-libs/pam-0.75-r4 sys-apps/pam-login ) ..."

pam-login-3.14.ebuild: DEPEND="... >=sys-apps/shadow-4.0.2-r5 ..."

It seems a bad thing, shouldn't one of them be PDEPEND?

pam-login doesnt really require shadow ... removed it from pam-login's DEPEND

(In reply to comment #12)
> pam-login doesnt really require shadow ... removed it from pam-login's DEPEND
> 

sys-apps/pam-login-4.0.14 requires >=sys-apps/shadow-4.0.11.1-r1

sys-apps/shadow-4.0.14-r2 requires !sys-apps/pam-login

So you can't install pam-login without shadow and you can't install shadow with
pam-login.

If you look at the DEPEND in shadow-4.0.14-r1 it says
!pam? ( !sys-apps/pam-login )

And in shadow-4.0.14-r2 it instead just says
!sys-apps/pam-login

Just to make it clear; the blocking issue only comes up starting with shadow
version 4.0.14-r2

Did you also happen to read the ChangeLog entry?

From comment #14:
> And in shadow-4.0.14-r2 it instead just says
> !sys-apps/pam-login

So it does in shadow-4.0.15-r2.ebuild that recently was marked stable. Now
sys-apps/pam-login blocks the update of 'system' -- a system I used (and
updated successfully) for months. 

Suggestions how to proceed?

(In reply to comment #16)
..
> Suggestions how to proceed?

This is not really the right bug.. But you simply want to.
emerge -C pam-login && emerge shadow