<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "http://bugs.gentoo.org/bugzilla.dtd">

<bugzilla version="2.22.7"
          urlbase="http://bugs.gentoo.org/"
          maintainer="bugzilla@gentoo.org"
>

    <bug>
          <bug_id>67815</bug_id>
          
          <creation_ts>2004-10-16 14:48 0000</creation_ts>
          <short_desc>remove PAM requirement in Gentoo</short_desc>
          <delta_ts>2006-06-02 04:06:29 0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>1</classification_id>
          <classification>Unclassified</classification>
          <product>Gentoo Linux</product>
          <component>Core system</component>
          <version>unspecified</version>
          <rep_platform>All</rep_platform>
          <op_sys>All</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>FIXED</resolution>
          
          
          
          <priority>P2</priority>
          <bug_severity>normal</bug_severity>
          <target_milestone>---</target_milestone>
          <dependson>35405</dependson>
          <blocked>69066</blocked>
          
          <everconfirmed>1</everconfirmed>
          <reporter>vapier@gentoo.org</reporter>
          <assigned_to>base-system@gentoo.org</assigned_to>
          <cc>clmason@gmail.com</cc>
    
    <cc>franke.daniel@gmail.com</cc>
    
    <cc>greg_g@gentoo.org</cc>
    
    <cc>solar@gentoo.org</cc>
    
    <cc>spock@trilithium.com</cc>

      

      
          <long_desc isprivate="0">
            <who>vapier@gentoo.org</who>
            <bug_when>2004-10-16 14:48:33 0000</bug_when>
            <thetext>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</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>code@edoceo.com</who>
            <bug_when>2004-10-26 13:46:24 0000</bug_when>
            <thetext>See also 69066</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>vapier@gentoo.org</who>
            <bug_when>2004-10-28 19:32:56 0000</bug_when>
            <thetext>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</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>sebastian_ml@gmx.net</who>
            <bug_when>2004-11-09 11:35:56 0000</bug_when>
            <thetext>Hi!

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

Thanks
Sebastian</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>vapier@gentoo.org</who>
            <bug_when>2004-11-09 21:38:53 0000</bug_when>
            <thetext>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</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>vapier@gentoo.org</who>
            <bug_when>2004-11-23 20:36:00 0000</bug_when>
            <thetext>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=&quot;
    pam? ( sys-libs/pam sys-apps/pam-login )
    !pam? ( !sys-apps/pam-login )
&quot;</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>ps.m@gmx.net</who>
            <bug_when>2004-11-25 00:14:28 0000</bug_when>
            <thetext>DEPEND=&quot;
    pam? ( sys-libs/pam sys-apps/pam-login )
    !pam? ( !sys-apps/pam-login )
&quot;
the above condition was entered as
DEPEND=&quot;
    pam? ( sys-libs/pam sys-apps/pam-login )
    !pam? ( sys-apps/pam-login ) /* w/o additional ! */
&quot;
and it pulls in pam-login for all cases (and pam-login depending on pam pulls 
pam also in)
uclibc killed
I can&apos;t disable RESOLVED FIXED, but it is not resolved fixed
All shadow versions stable and up are involved</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>solar@gentoo.org</who>
            <bug_when>2004-11-25 06:57:45 0000</bug_when>
            <thetext>Reopeing bug per comment #6
Attempting to verify.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>solar@gentoo.org</who>
            <bug_when>2004-11-25 07:26:09 0000</bug_when>
            <thetext>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=&quot;pam selinux nls skey&quot;
 
 RDEPEND=&quot;&gt;=sys-libs/cracklib-2.7-r3
 	pam? ( &gt;=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 )&quot;
 DEPEND=&quot;${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=&quot;pam selinux nls skey&quot;
 
 RDEPEND=&quot;&gt;=sys-libs/cracklib-2.7-r3
 	pam? ( &gt;=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 )&quot;
 DEPEND=&quot;${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=&quot;pam selinux nls skey&quot;
 
 RDEPEND=&quot;&gt;=sys-libs/cracklib-2.7-r3
 	pam? ( &gt;=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 )&quot;
 DEPEND=&quot;${DEPEND}
</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>solar@gentoo.org</who>
            <bug_when>2004-11-25 07:39:07 0000</bug_when>
            <thetext>InCVS
Looks good from native uclibc(-pam) and native glibc(+pam) envs.

changing resolution to FIXED</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>solar@gentoo.org</who>
            <bug_when>2004-11-26 15:37:15 0000</bug_when>
            <thetext>*** Bug 72411 has been marked as a duplicate of this bug. ***</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>greg_g@gentoo.org</who>
            <bug_when>2004-11-27 15:40:43 0000</bug_when>
            <thetext>Now we have:

shadow-4.0.x.ebuild: RDEPEND=&quot;... pam? ( &gt;=sys-libs/pam-0.75-r4 sys-apps/pam-login ) ...&quot;

pam-login-3.14.ebuild: DEPEND=&quot;... &gt;=sys-apps/shadow-4.0.2-r5 ...&quot;

It seems a bad thing, shouldn&apos;t one of them be PDEPEND?</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>vapier@gentoo.org</who>
            <bug_when>2004-11-29 17:15:41 0000</bug_when>
            <thetext>pam-login doesnt really require shadow ... removed it from pam-login&apos;s DEPEND</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>cslycord@gmail.com</who>
            <bug_when>2006-03-13 19:02:28 0000</bug_when>
            <thetext>(In reply to comment #12)
&gt; pam-login doesnt really require shadow ... removed it from pam-login&apos;s DEPEND
&gt; 

sys-apps/pam-login-4.0.14 requires &gt;=sys-apps/shadow-4.0.11.1-r1

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

So you can&apos;t install pam-login without shadow and you can&apos;t install shadow with pam-login.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>cslycord@gmail.com</who>
            <bug_when>2006-03-13 19:09:35 0000</bug_when>
            <thetext>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</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>solar@gentoo.org</who>
            <bug_when>2006-03-13 19:23:15 0000</bug_when>
            <thetext>Did you also happen to read the ChangeLog entry?</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>franke.daniel@gmail.com</who>
            <bug_when>2006-05-31 23:56:12 0000</bug_when>
            <thetext>From comment #14:
&gt; And in shadow-4.0.14-r2 it instead just says
&gt; !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 &apos;system&apos; -- a system I used (and updated successfully) for months. 

Suggestions how to proceed?</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>solar@gentoo.org</who>
            <bug_when>2006-06-02 04:06:29 0000</bug_when>
            <thetext>(In reply to comment #16)
..
&gt; Suggestions how to proceed?

This is not really the right bug.. But you simply want to.
emerge -C pam-login &amp;&amp; emerge shadow
</thetext>
          </long_desc>
      
    </bug>

</bugzilla>