www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gavin (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (INFRA-5384) Incorrect restriction in modify_committee.pl ?
Date Sat, 13 Oct 2012 00:21:02 GMT

     [ https://issues.apache.org/jira/browse/INFRA-5384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Gavin closed INFRA-5384.

    Resolution: Fixed
      Assignee:     (was: Gavin)

1. Done.

2. Not worth it, easy enough for infra to handle on the very odd occasion it is needed.

When a rename of the acct was done this part was missed, thats all.
> 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
> 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

View raw message