On that note, I notice that the post-review debug output shows the
relative path as /trunk. Is this expected? That is, will post-review
strip the '/' off the repository path and any characters following
this repository path are considered the base path? I'll check our
reviewboard server to double check.
On Thu, Jun 24, 2010 at 3:26 PM, Christian Hammond chip...@chipx86.com wrote:
Hi Edwin,
There shouldn't be any caches for this. The error means literally that there
is no Repository matching the path provided in either its Path or Mirror
Path fields. Make sure that there isn't some off-by-one somewhere (a
trailing / where there shouldn't be, or where there should be, etc.). It
must be exactly the same to the character.
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com
On Tue, Jun 22, 2010 at 9:07 AM, Edwin Vane rev...@gmail.com wrote:
Hi,
We recently moved our svn server (or at least the DNS alias was
changed). Every developer did an svn switch --relocate old_location
new_location. The reviewboard server was updated too so that the new
paths were associated with recognized repositories.
Reviews submitted via the web interface have no problems. However, if
I use post-review I get the following error:
Error creating review request: The repository path specified is not in
the list of known repositories (code 206)
The debug output from post-review is as follows:
svn info
repository info: Path: http://new.server.com/path/to/repo, Base path:
/trunk, Supports changesets: False
svn propget reviewboard:url /home/revane/work
svn diff --diff-cmd=diff
Looking for 'local.reviewboard.server.com /' cookie in
/home/revane/.post-review-cookies.txt
Loaded valid cookie -- no login required
Attempting to create review request for None
HTTP GETting /api/json/repositories/
HTTP GETting /api/json/repositories/3/info/
HTTP GETting /api/json/repositories/4/info/
HTTP GETting /api/json/repositories/5/info/
HTTP GETting /api/json/repositories/1/info/
repository info: Path: http://new.server.com/path/to/repo, Base path:
/trunk, Supports changesets: False
HTTP POSTing to
http://local.reviewboard.server.com/api/json/reviewrequests/new/:
{'repository_path': u'http://new.server.com/path/to/repo'}
Error creating review request: The repository path specified is not in
the list of known repositories (code 206)
So it appears that the correct repository path is being sent. For some
reason the server is refusing it. Is there a cache in the server
configuration that needs to be wiped? Is JSON stuff cached somewhere
(perhaps even on the client) and this needs to be wiped? Is there more
debug options I can try to help identify the problem? Any help would
be appreciated. I'd love to be using post-review again.
Edwin V
--
Want to help the Review Board project? Donate today at
http://www.reviewboard.org/donate/
Happy user? Let us know at http://www.reviewboard.org/users/
-~--~~~~--~~--~--~---
To unsubscribe from this group, send email to
reviewboard+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/reviewboard?hl=en
--
Want to help the Review Board project? Donate today at
http://www.reviewboard.org/donate/
Happy user? Let us know at http://www.reviewboard.org/users/
-~--~~~~--~~--~--~---
To unsubscribe from this group, send email to
reviewboard+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/reviewboard?hl=en
--
Edwin V
--
Want to help the Review Board project? Donate today at
http://www.reviewboard.org/donate/
Happy user? Let us know at http://www.reviewboard.org/users/
-~--~~~~--~~--~--~---
To unsubscribe from this group, send email to
reviewboard+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/reviewboard?hl=en
