If we limit it to the virtual, pam and pambase, I'm happy to stick maintaining them, the others I don't use, which is why I don't care about them as much.
Diego Elio Pettenò — Flameeyes flamee...@flameeyes.eu — http://blog.flameeyes.eu/ On 11 January 2014 11:01, Pacho Ramos <pa...@gentoo.org> wrote: > El sáb, 11-01-2014 a las 10:57 +0000, Markos Chandras escribió: > > On 01/10/2014 11:14 PM, Diego Elio Pettenò wrote: > > > On 10 January 2014 22:20, Mike Frysinger <vap...@gentoo.org> wrote: > > > > > >> how would moving it to base-system make any difference ? people > doing it > > >> wrong > > >> wouldn't really care which herd pam itself is owned by. > > >> > > > > > > I'm not saying it makes a difference, sorry I didn't make it clear. > > > > > > > > > Diego Elio Pettenò — Flameeyes > > > flamee...@flameeyes.eu — http://blog.flameeyes.eu/ > > > > > I only suggested that as part of our usual 'drop-dead-teams' process in > > the retirement team. So in this case, either a 'parent' herd needs to > > inherit the packages or simply drop them to maintainer-needed > > > sys-auth/pam-pgsql > sys-auth/pam_dotfile > sys-auth/pam_krb5 > sys-auth/pam_ldap > sys-auth/pam_passwdqc > sys-auth/pam_ssh > sys-auth/pam_ssh_agent_auth > sys-auth/pambase > sys-libs/pam > virtual/pam > > This are the packages under pam team management, would be nice to know > if there is somebody maintaining each of them or we need new maintainer > for any > > Thanks > > > >
