Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 2714 by gh.capon...@gmail.com: I'm not able to upload a diff file using ClearCase as Repository.
http://code.google.com/p/reviewboard/issues/detail?id=2714

* NOTE: Do not post confidential information in this bug report. *
*       If you need immediate support, please contact            *
*       reviewbo...@googlegroups.com                             *

What version are you running?
1.6.11

What's the URL of the page containing the problem?
New Review Request

What steps will reproduce the problem?
1. Trying to upload a diff file using UI or post-review

What is the expected output? What do you see instead?
The expected output would be the diff file being uploaded properly.

What operating system are you using? What browser?
Windows 7 - Google Chrome

Please provide any additional information below.

When I set a Snapshot View as Repository, I can't upload directly the diff file. The "New Review Request" UI complains that the diff file is not in a valid diff format (diff generated with cleartool). So I tried with post-review and I get the error 207 - The file was not found in the repository.
With the --output-diff parameter I'm able to see the diff file.

When I try with a Dynamic View, I can't even see the repository on "New Review Request". It shows only “None - Graphics Only” for repository, but the repository was added and marked to be shown in administrator area. And, of course, if I try using post-review I get The error 206 - The repository path specified is not in the list of known repositories
With the --output-diff parameter I'm able to see the diff file.

Any ideas?

Thanks in advance.

--
You received this message because you are subscribed to the Google Groups 
"reviewboard-issues" group.
To post to this group, send email to reviewboard-issues@googlegroups.com.
To unsubscribe from this group, send email to 
reviewboard-issues+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/reviewboard-issues?hl=en.

Reply via email to