If svn/Repo1, svn/Repo2, etc. are all independent Subversion repositories, and
not subdirectories within a larger repository, then you should have a
repository entry in Review Board for each.
You shouldn't target trunk, branches, etc., because those are subdirectories.
When posting a change for review against a Subversion repository, RBTools will
send paths that are relative to the root of the repository (say,
/trunk/myproject/README). That then gets accessed relative to the repository
path, giving you something like
https://vcs.ourdomain.com/svn/Repo1/trunk/myproject/README, or, if
misconfigured, something like
To fix things up by hand, you'll need to modify the diffviewer_filediff table
entries (or FileDiff in the database editor in the admin UI) and change the
paths shown there. The trick is associating the entries with a given review
request. For that, you can try something like:
$ rb-site manage /path/to/site shell
>>> from reviewboard.diffviewer.models import FileDiff
>>> print FileDiff.objects.filter(diffset__history__review_request=<review
request ID>).values_list('pk', 'source_file')
Where "<review request ID>" is replaced with the numeric ID of the review
reuqest. That would show you all FileDiff IDs and their paths for a given
Christian Hammond - christ...@beanbaginc.com
Review Board - https://www.reviewboard.org
Beanbag, Inc. - https://www.beanbaginc.com
From: Papaswede <papasw...@gmail.com>
Reply: email@example.com <firstname.lastname@example.org>>
Date: May 28, 2015 at 2:32:20 PM
To: email@example.com <firstname.lastname@example.org>>
Subject: Re: After upgrading to ReviewBoard 2.0.15 the existing reviews do not
display the diffs correctly
> Ok, thank you.
> If I wanted to go through and fix the paths of the existing reviews, which
> tables, specifically, would I need to go through and look at?
> Aslo, this may be a dumb question, but I'm not the most Subversion savvy
> person in the world. We have our repositories set up like
> and then we have the Repositories within there, like
> and then each repository has
> Are you saying we'd need to point straight to
> https://vcs.ourdomain.com/svn/Repo1/ in order for Reviewboard to work
> correctly, or can we target trunk or individual branches, etc.?
> On Wednesday, May 27, 2015 at 12:28:40 PM UTC-4, Papaswede wrote:
>> I upgraded ReviewBoard from 1.6.11 to 2.0.15. After doing this, I get
>> error messages when attempting to view the diffs of the existing reviews. I
>> get messages like:
>> The file
>> path not found", 160013)' could not be found in the repository
>> Where that path definitely is not a valid svn path. It should
>> So, it's like there's stuff being automatically inserted into the svn path
>> for the file, but I have no idea why as it was working on version 1.6.11.
>> Any help would be greatly appreciated.
> Supercharge your Review Board with Power Pack:
> Want us to host Review Board for you? Check out RBCommons:
> Happy user? Let us know! https://www.reviewboard.org/users/
> You received this message because you are subscribed to the Google Groups
> To unsubscribe from this group and stop receiving emails from it, send an
> email to reviewboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
Supercharge your Review Board with Power Pack:
Want us to host Review Board for you? Check out RBCommons:
Happy user? Let us know! https://www.reviewboard.org/users/
You received this message because you are subscribed to the Google Groups
To unsubscribe from this group and stop receiving emails from it, send an email
For more options, visit https://groups.google.com/d/optout.