#10698 closed task (invalid)
Support for Trac 1.0
Reported by: | Owned by: | Emmanuel Blot | |
---|---|---|---|
Priority: | normal | Component: | LdapPlugin |
Severity: | major | Keywords: | group |
Cc: | Trac Release: | 1.0 |
Description
LdapPlugin seems not working on Trac 1.0
Attachments (0)
Change History (12)
comment:1 Changed 12 years ago by
comment:2 Changed 12 years ago by
Maybe this might help?
17:20:51 Trac[loader] DEBUG: Loading ldapplugin.api from /usr/lib/python2.6/site-packages/LdapPlugin-0.6.0dev_r5686-py2.6.egg 17:20:51 Trac[loader] ERROR: Skipping "ldapplugin.api = ldapplugin.api": (version conflict "VersionConflict: (Trac 1.0 (/usr/lib/python2.6/site-packages/Trac-1.0-py2.6.egg), Requirement.parse('Trac<0.13'))")
comment:3 Changed 12 years ago by
The plugin author imposed that restriction in [10934]. I suggest deleting install_requires = [ 'Trac>=0.12', 'Trac<0.13']
from setup.py
and seeing if it just works. There's a good chance it will.
comment:4 follow-up: 5 Changed 11 years ago by
I tried that: set install_requires = [ 'Trac>=0.12' ]
in setup.py, built and installed the plugin, configured and enabled it. When I did that, every query to Trac hung and never came back. I tried setting log_level=DEBUG
, but got nothing at all from the plugin in the Trac log.
comment:5 Changed 11 years ago by
Replying to andrex:
When I did that, every query to Trac hung and never came back. I tried setting
log_level=DEBUG
, but got nothing at all from the plugin in the Trac log.
Do you mean that the Trac pages don't load?
comment:6 Changed 11 years ago by
Resolution: | → invalid |
---|---|
Status: | new → closed |
Yes, that's what I meant.
But it turns out that this was caused by a misconfiguration of my LDAP settings. Trac was trying to contact my server on an LDAPS port, with use_tls = false. The connection hung, and so did Trac. So that was my fault, not the plugin's.
With my LDAP settings corrected and with the above modification, the plugin does work fine in Trac 1.0. Unfortunately though, it causes a long delay on first load, or whenever the LDAP cache expires.
Sorry for the noise.
comment:7 follow-up: 8 Changed 11 years ago by
eblot: is it okay if we remove the restriction Trac < 0.13
, since the 0.12
branch of the plugin has been reported to work with Trac 1.0?
comment:8 follow-up: 10 Changed 11 years ago by
comment:9 Changed 11 years ago by
comment:10 follow-up: 11 Changed 11 years ago by
Replying to eblot:
Feel free: I have no time to work on this plugin anymore.
Thanks. Shall I tag it with needsadoption, or do you think you might return to it someday?
I've tagged the project wiki page with 1.0
and added a note about the 0.7.x
series working with Trac 1.0
.
comment:11 follow-up: 12 Changed 11 years ago by
Replying to rjollos:
Thanks. Shall I tag it with needsadoption, or do you think you might return to it someday?
Sure, you can. I thought it had been already 'adopted'.
comment:12 Changed 11 years ago by
Replying to eblot:
Sure, you can. I thought it had been already 'adopted'.
Not that I know of. I don't see any other committers or tickets requesting adoption.
What errors or problems do you see? The plugin author will certainly need more details than you've provided!