www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Thomas (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (INFRA-4922) Python ldap has stopped working on minotaur/people
Date Tue, 04 Jun 2013 11:44:21 GMT

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

Mark Thomas resolved INFRA-4922.

    Resolution: Fixed

I've confirmed that import ldap no longer generates an error on people.a.o.
The security/cyrus-sasl2 was not required (and trying to use it caused all sorts of issues
for other ports).
> Python ldap has stopped working on minotaur/people
> --------------------------------------------------
>                 Key: INFRA-4922
>                 URL: https://issues.apache.org/jira/browse/INFRA-4922
>             Project: Infrastructure
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>         Environment: minotaur/people
>            Reporter: Sebb
> The Python ldap module seems to have got lost in the recent restart/upgrade of minotaur.
> This causes problems for the people application run by apsite:
> The apsite build is failing with:
>  File "./keys-fetch.py", line 28, in <module>
>    import ldap
> ImportError: No module named ldap
> This will probably also affect some infra scripts, if they are run on minotaur (for example
generate-dotqmail-availid.py uses ldap)

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