You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@infra.apache.org by "Gavin (JIRA)" <ji...@apache.org> on 2012/10/13 02:19:03 UTC
[jira] [Assigned] (INFRA-5384) Incorrect restriction in
modify_committee.pl ?
[ https://issues.apache.org/jira/browse/INFRA-5384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gavin reassigned INFRA-5384:
----------------------------
Assignee: Gavin
> Incorrect restriction in modify_committee.pl ?
> ----------------------------------------------
>
> Key: INFRA-5384
> URL: https://issues.apache.org/jira/browse/INFRA-5384
> Project: Infrastructure
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: LDAP
> Reporter: Sebb
> Assignee: Gavin
>
> There was a problem with the setup for the account for Joerg Ehrlich; his login was set up as ehrlich, but iclas.txt showed erlich (I've fixed that) and the tika committee LDAP group includes both erlich and ehrlich.
> So I emailed the Tika chair (Dave Meikle) to ask him to remove the spurious entry.
> He has tried this, but it does not work:
> $ modify_committee.pl tika -rm jerlich
> Found 0 people matching uid=jerlich!
> Yet I get:
> pwd ~ : list_committee.pl tika
> amylka
> dmeikle
> ingo
> jehrlich
> jerlich
> jerome
> jnioche
> <snip/>
> Two fixes needed here please:
> 1) remove spurious erlich entry from Tika PMC group
> 2) ensure spurious entries can be removed from groups; (some of) the validation needs to be skipped when doing a remove.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira