id summary reporter owner description type status priority component severity resolution keywords cc release 3962 MergeInfoEnhancer has error with merges from SVN 1.4.x smrobinson62@… Emmanuel Blot "I've installed Revtree 0.5.16 ./tracrevtreeplugin-0.5.16dev_r4012-py2.5.egg[[br]] ./tracrevtreemergeinfoenhancer-0.1.0dev_r3580-py2.5.egg on both a test server and a production server running Trac 0.11.1 ./trac-0.11.1-py2.5.egg[[br]] ./genshi-0.5.1-py2.5-win32.egg served by Apache httpd 2.2.9 on Windows. When I have !MergeInfoEnhancer disabled, all is well. When I enable it on the test server running Subversion 1.5.3, which does have some branches/tags/merges from 1.4.x and recent branches/merges from 1.5.3, it works as advertised. However, when I enable !MergeInfoEnhancer on the production server which has branches/tags/merges mostly from 1.4.x and recent merges using 1.5.3, I get the following errors depending in the time range I chose. Error: No such node[[br]] No node RB1.3 at revision 3049 Error: No such node[[br]] No node RB1.3 at revision 3084 Error: No such node[[br]] No node tags/1.2.9 at revision 2181 No errors are recorded in Trac logs. I re-sync'd the Trac DBs ""just in case"". The changesets in branch RB1.3 are not for branches/tags. However, changesets 3050 and 3085, the next ones, are for creating tags from the branch RB1.3. Changeset 2181 is for the removal of tag/1.2.9 (to clear out a mistake) but 2182 is the creation of tag/1.2.9 from branch RB1.3 again. So it sounds like changesets/revisions are 1 off somewhere in !MergeInfoEnhancer. These nodes display just fine when !MergeInfoEnhancer is disabled. I tried using Revtree 0.6.0 from rev. 4024 with code changes suggested in another ticket, but then no merge info was displayed, even on the test server where it is displayed with 0.5.16. There is no error and the tree looks correct for trunk/branches/tags." defect closed normal RevtreePlugin normal wontfix 0.11