You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Mark Thomas (JIRA)" <ji...@apache.org> on 2013/06/03 10:06:21 UTC

[jira] [Commented] (INFRA-4922) Python ldap has stopped working on minotaur/people

    [ https://issues.apache.org/jira/browse/INFRA-4922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13672884#comment-13672884 ] 

Mark Thomas commented on INFRA-4922:
------------------------------------

security/cyrus-sasl2 looks to be a red herring. py-ldap2 builds for other machines without SASL.
                
> 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