From: Pacho Ramos <pacho@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: About pam herd status
Date: Sat, 11 Jan 2014 12:01:29 +0100 [thread overview]
Message-ID: <1389438089.1141.20.camel@belkin5> (raw)
In-Reply-To: <52D1237C.50307@gentoo.org>
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 <vapier@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
> > flameeyes@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
next prev parent reply other threads:[~2014-01-11 11:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-09 14:20 [gentoo-dev] About pam herd status Pacho Ramos
2013-12-09 14:21 ` [gentoo-dev] " Diego Elio Pettenò
2013-12-09 14:22 ` Andreas K. Huettel
2013-12-09 21:32 ` Markos Chandras
2014-01-09 20:20 ` Mike Frysinger
2014-01-09 20:22 ` Markos Chandras
2014-01-09 20:24 ` Diego Elio Pettenò
2014-01-10 22:20 ` Mike Frysinger
2014-01-10 23:14 ` Diego Elio Pettenò
2014-01-11 10:57 ` Markos Chandras
2014-01-11 11:01 ` Pacho Ramos [this message]
2014-01-11 11:07 ` Diego Elio Pettenò
2014-01-11 11:15 ` Markos Chandras
2014-01-11 11:15 ` Pacho Ramos
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1389438089.1141.20.camel@belkin5 \
--to=pacho@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox