Modify

Opened 8 years ago

Closed 7 years ago

#1090 closed defect (fixed)

RevTreePlugin Installation issue

Reported by: anonymous Owned by: eblot
Priority: normal Component: RevtreePlugin
Severity: normal Keywords: needinfo
Cc: Trac Release: 0.11

Description

This is probably an installation or configuration issue, and not a defect.

I have recently installed RevTreePlugin (from the SVN tree) into Trac 0.10.2, enabled it and attempted to use it from the menu. I receive the following error:

Traceback (most recent call last):

File "/usr/lib/python2.4/site-packages/trac/web/main.py", line 387, in dispatch_request

dispatcher.dispatch(req)

File "/usr/lib/python2.4/site-packages/trac/web/main.py", line 238, in dispatch

resp = chosen_handler.process_request(req)

File "build/bdist.linux-i686/egg/revtree/web_ui.py", line 185, in process_request File "build/bdist.linux-i686/egg/revtree/web_ui.py", line 313, in _process_revtree File "build/bdist.linux-i686/egg/revtree/model.py", line 362, in build File "build/bdist.linux-i686/egg/revtree/model.py", line 111, in build

NameError: global name 'revision' is not defined

Any guidance is appreciated.

Thanks - this plugin really looks awesome, and I am hopeful I can get mine working.

Attachments (0)

Change History (7)

comment:1 follow-up: Changed 8 years ago by eblot

  • Keywords needinfo added; RevTreePlugin removed

Yep sorry the exception message was in trouble. Fixed up in [1859]

Anyway, this won't solve your initial issue (you will get another error message). Maybe your branch regular expression is invalid, or it does not match your actual subversion repository structure.

What kind of repository structure are you using? The default branch reg ex expects something like this:

  /trunk
  /branches/

BTW, do not forget to enclose Python traceback in {{{ }}} block to prevent from wiki formatting the trace.

comment:2 in reply to: ↑ 1 ; follow-up: Changed 8 years ago by anonymous

Replying to eblot:

Yep sorry the exception message was in trouble. Fixed up in [1859]

Anyway, this won't solve your initial issue (you will get another error message). Maybe your branch regular expression is invalid, or it does not match your actual subversion repository structure.

What kind of repository structure are you using? The default branch reg ex expects something like this:

  /trunk
  /branches/

BTW, do not forget to enclose Python traceback in {{{ }}} block to prevent from wiki formatting the trace.

Thanks very much. The new version of the plugin is producing a much more sensible error message, and it is indeed pointing to the branch structure.

The exact error indicates that a check is being made to compare the trunk to a branch, and that this comparison is failing (returning false).

AssertionError: Incoherent path [trunk] != [branches/my-branch-name-here] rev: 107

Is this comparison actually being made? If so, any guidance on resolving this? The trunk should match the branch-point at that point, but nowhere esle. Am I missing a key concept here?

comment:3 in reply to: ↑ 2 ; follow-up: Changed 8 years ago by eblot

Replying to anonymous:

Is this comparison actually being made? If so, any guidance on resolving this? The trunk should match the branch-point at that point, but nowhere esle. Am I missing a key concept here?

This kind of error is usually triggered when a changeset is detected as 'incoherent' for the revtree plugin:
A single changeset should not contain changes that impact files in different branches

  • if a changeset contains file/directory changes in /trunk/.. it cannot also contain changes for another branch such as /branches/my-branch-name-here

Can you post here the list of changes for the revision which is in trouble (107)? You can obtain it with the following command:

svn log -v -r 107 url_to_repos

in order to check up the content of the revision in trouble?

comment:4 Changed 8 years ago by eblot

  • Status changed from new to assigned

comment:5 in reply to: ↑ 3 ; follow-up: Changed 8 years ago by kate.yoak@…

This kind of error is usually triggered when a changeset is detected as 'incoherent' for the revtree plugin:
A single changeset should not contain changes that impact files in different branches

I am getting a similar error. I examined the changeset in question and found that it contained all the files initially placed into branches/development but also the creation of branches/integration directory. So what can I do to fix the problem? Am I out of luck in using revtree on this particular project?

comment:6 in reply to: ↑ 5 Changed 8 years ago by eblot

Replying to kate.yoak@farheap.com:

I am getting a similar error.

See also #1284 and #1354 that deal with this specific issue.

So what can I do to fix the problem? Am I out of luck in using revtree on this particular project?

The latest version [2111] of the plugin (for Trac 0.11) has been modified to cope with such incoherent paths. However, as said in the RevtreePlugin page, the plugin is not actively maintained for the current release of Trac (0.10) and this enhancement has not been backported to this version.

So you're basically facing two choices:

  1. Upgrade to 0.11
  2. Set revbase in your trac.ini file to the immediate superior changeset of the one in trouble: the plugin won't consider any revision before revbase, so you'll be able to render any changeset that has been committed after the changeset in error.

comment:7 Changed 7 years ago by eblot

  • Resolution set to fixed
  • Status changed from assigned to closed
  • Trac Release changed from 0.10 to 0.11

Fixed for t:milestone:0.11, will not be fixed for t:milestone:0.10

If someone wants to provide a patch for 0.10 (i.e. backport the changes made for the 0.11), I'll be happy to commit them to the repository.

Add Comment

Modify Ticket

Action
as closed The owner will remain eblot.
The resolution will be deleted. Next status will be 'reopened'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.