Summary: | pam-bugs: no reply to project status mail | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Michał Górny <mgorny> |
Component: | Current packages | Assignee: | PAM Gentoo Team (OBSOLETE) <pam-bugs+disabled> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | base-system, pacho, robbat2 |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Michał Górny
2017-08-12 06:53:52 UTC
Looking at the status of pambase and other pam maintained packages... it seems thet project is not much attended :/ I will CC robbat2 as he is the only member currently to check if he wants to keep the project or simply move the packages to maintainer-needed and pick what he wants to maintain Ok, so here's what I propose. Technically, I don't think there's much of a reason to have a project overseeing random PAM modules. Therefore: 1. Send 'up for grabs' to find/encourage individual maintainers for all the packages. 2. Optionally, move the most important packages (pambase and linux-pam) to base-system. (@base-system, what do you think?) 3. Eventually, disband the project. (In reply to Michał Górny from comment #2) > > 2. Optionally, move the most important packages (pambase and linux-pam) to > base-system. (@base-system, what do you think?) > Personally I have no issues with that. AFAIK they are low-maintenance so no big burden for us. (In reply to Michał Górny from comment #2) > Ok, so here's what I propose. Technically, I don't think there's much of a > reason to have a project overseeing random PAM modules. Therefore: > > 1. Send 'up for grabs' to find/encourage individual maintainers for all the > packages. > > 2. Optionally, move the most important packages (pambase and linux-pam) to > base-system. (@base-system, what do you think?) > > 3. Eventually, disband the project. actually I do pam itself alone, and would like to go on alone as well The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=7fefc74a22da5151f1475d91a0e36b5396823700 commit 7fefc74a22da5151f1475d91a0e36b5396823700 Author: Michał Górny <mgorny@gentoo.org> AuthorDate: 2019-03-28 06:05:21 +0000 Commit: Michał Górny <mgorny@gentoo.org> CommitDate: 2019-03-28 06:05:21 +0000 */*: Remove pam-bugs@ from maintainers Bug: https://bugs.gentoo.org/627640 Signed-off-by: Michał Górny <mgorny@gentoo.org> sys-apps/shadow/metadata.xml | 6 +----- sys-auth/pam-afs-session/metadata.xml | 5 +---- sys-auth/pam-pgsql/metadata.xml | 4 +--- sys-auth/pam_abl/metadata.xml | 5 +---- sys-auth/pam_blue/metadata.xml | 5 +---- sys-auth/pam_chroot/metadata.xml | 5 +---- sys-auth/pam_dotfile/metadata.xml | 4 +--- sys-auth/pam_fprint/metadata.xml | 4 +--- sys-auth/pam_krb5/metadata.xml | 3 --- sys-auth/pam_ldap/metadata.xml | 4 +--- sys-auth/pam_mktemp/metadata.xml | 4 ---- sys-auth/pam_p11/metadata.xml | 4 ---- sys-auth/pam_passwdqc/metadata.xml | 4 +--- sys-auth/pam_radius/metadata.xml | 5 +---- sys-auth/pam_skey/metadata.xml | 4 ---- sys-auth/pam_ssh/metadata.xml | 4 +--- sys-auth/pam_ssh_agent_auth/metadata.xml | 4 +--- sys-auth/pambase/metadata.xml | 3 --- sys-auth/passwdqc/metadata.xml | 4 +--- sys-libs/pam/metadata.xml | 4 ---- virtual/pam/metadata.xml | 3 --- 21 files changed, 14 insertions(+), 74 deletions(-) Ok, so as discussed I've added zlogene to pambase, removed pam-bugs@ everywhere, sent 'up for grabs' and tried my best reassigning bugs. I've left pam-bugs@ in CC everywhere to ease tracking of reassigned bugs. Please let me know if you want to keep pam-bugs@ alias alive for a while more, or if I should start disbanding the project's resources. Wiki project page removed. Will rename bugzilla alias now. |