How do you have the server configured? The server needs to point to a
dynamic view where it will be able to access the file revisions
specified via extended path notation.
Dan
On Feb 17, 10:15 am, eeiths wrote:
> Ok, i got to spend a little time at this today.
>
> looks like postreview has suppo
Ok, i got to spend a little time at this today.
looks like postreview has support for clearcase on windows without
cygwin.
Ans so the posted diff looks fine.
Sorry my mistake.
But thats not the case on the server side.
It fails on the file_exists and then trying to view the diff it
uses a differe
i've got a bit further with this...it looks like the
tool.file_exists(filename, revision) on the server side fails
It tries to parse a file name form the clearcase extended name i.e.
the one with the versions and @@ char sequences
included in the path. e.g Y:/wran_cm_cms/@@/main/22/src/@@/main/3/co
I guess You are using 1.0.x ReviewBoard. I had similar problem last
time but my version was 1.1.x alpha which return additional
informations. My error while uploading diff looks like:
>>> {'fields': {'path': ['The diff file is empty']}, 'stat': 'fail', 'err':
>>> {'msg': 'One or more fields had e
You can use post-review --output-diff to generate the diff without pushing
it to the server.
What version is running on the server? You may be able to find some data in
the log files, if you turn logging on.
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewbo
I'm trying the post-review tool on windows env but i get the following
error ...wondering is this a clearcase issue or reviewboard.
is the a command to create the diff in isolation ..so I can see or
upload it via the GUI.
How can i debug the server side ..?
Any help appreciated .
C:\python25\Scr
