Hi !
During the week end I created at Bibucket a fork of Trac XmlRpcPlugin
to add in there compatibility for Bloodhound . We need that to
integrate some desktop applications with issue tracker , but there are
other applications even for our own use .
After reviewing the state of xmlrpcplugin trunk , now I tried to run
its test suite . This is what I got
{{{
#!sh
$ /srv/venv/python/trac/0.13/bin/python setup.py test -m tracrpc.tests
running test
running egg_info
writing TracXMLRPC.egg-info/PKG-INFO
writing top-level names to TracXMLRPC.egg-info/top_level.txt
writing dependency_links to TracXMLRPC.egg-info/dependency_links.txt
writing entry points to TracXMLRPC.egg-info/entry_points.txt
writing TracXMLRPC.egg-info/PKG-INFO
writing top-level names to TracXMLRPC.egg-info/top_level.txt
writing dependency_links to TracXMLRPC.egg-info/dependency_links.txt
writing entry points to TracXMLRPC.egg-info/entry_points.txt
reading manifest file 'TracXMLRPC.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
writing manifest file 'TracXMLRPC.egg-info/SOURCES.txt'
running build_ext
Found Trac source: /path/to/bloodhound/trac
/srv/venv/python/trac/0.13/bin/python: can't open file
'/path/to/bloodhound/trac/contrib/htpasswd.py': [Errno 2] No such file
or directory
Unable to setup admin password
Trac test infrastructure not available.
Install Trac as 'python setup.py develop' (run Trac from source).
Stopping web server...
----------------------------------------------------------------------
Ran 0 tests in 0.000s
OK
}}}
So I'm curious : what's the estimated time to bring contrib folder
back into BH trunk ? <= if such estimation is possible of course .
--
Regards,
Olemis.
