Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
Bo (and others),
I'm just testing a new version of cvsgraph that Bertho has put together...
this version is tollerates 'properties' in the wrong place :-)
> Even more functional break problems:
> It turns out that the annotate function in ViewCvs is now also
> broken...
I get something like this:
Traceback (most recent call last):
File "/var/www/intranet/viewcvs/lib/viewcvs.py", line 3394, in main
request.run_viewcvs()
File "/var/www/intranet/viewcvs/lib/viewcvs.py", line 370, in run_viewcvs
self.view_func(self)
File "/var/www/intranet/viewcvs/lib/viewcvs.py", line 2077, in
view_annotate
diff_url, include_url, rev)
File "/var/www/intranet/viewcvs/lib/blame.py", line 453, in __init__
revision = parser.parse_cvs_file(repos.rcsfile(path_parts, 1), opt_rev)
File "/var/www/intranet/viewcvs/lib/blame.py", line 280, in parse_cvs_file
rcsparse.Parser().parse(rcsfile, self)
File "/var/www/intranet/viewcvs/lib/vclib/ccvs/rcsparse/common.py", line
282, in parse
self.parse_rcs_tree()
File "/var/www/intranet/viewcvs/lib/vclib/ccvs/rcsparse/common.py", line
230, in parse_rcs_tree
raise RCSExpected(sym, 'next')
RCSExpected: ('properties', 'next')
Which tends to indicate it is that pesky 'properties' in the wrong place
error. Looks like somebody will have to hack the viewcvs code (don't look at
me, I don't really do python)... either that, or write some code to repair
the affected files in a cvsnt repository.
Greetings from Luxembourg,
David.