Re: problem with post-review when mercurial and clearcase installed on server

2010-07-14 Thread Igor
It is quite clear what is going on... I wonder if it is considered as an option to move to .reviewboardrc file parameters like: client type (ClearCase, Git, Mercurial etc) ccroot_path viewinfo viewtype On Jul 13, 9:52 pm, Vesterbaek vesterb...@gmail.com wrote: Try doing a post-review -d to

Re: problem with post-review when mercurial and clearcase installed on server

2010-07-14 Thread Jan Koprowski
Look at my (jan.koprowski) patches at http://reviews.reviewboard.org/ to ClearCase. --repository-url allow point ccroot_path On Wed, Jul 14, 2010 at 2:26 PM, Igor xrevol...@gmail.com wrote: It is quite clear what is going on... I wonder if it is considered as an option to move to .reviewboardrc

Re: rb-site install - Review Board is taking a nap

2010-07-14 Thread Daniel
Anyone have any further suggestions on how to debug 'ReviewBoard is taking a nap' after a fresh install? Maybe there are some diagnostics I can run on my reviewboard site instance using rb-site manage or shell? I've tried validate and test, results are below (there was a problem running test)

Is git-svn supposed to work with --parent?

2010-07-14 Thread Jared Roberts
I'm new to reviewboard, so maybe I have totally the wrong idea. My org uses svn, but I'm using git-svn. I have a chain of commits in my git repos, and I want to post them as separate review requests, but I can't seem to get post-review to do this. My git repos looks like this: O -- change-3 |

RE: Error uploading diff: One or more fields had errors (105) - Errors during command execution( p4 login )

2010-07-14 Thread Dana Lacoste
Sorry, I was away for a few days, so I didn't reply right away Here's your debug steps: On the _SERVER_ side of ReviewBoard, run the command p4 info. It should connect to perforce and show you something like this: User name: p4user Client name: p4clientspecname Client host:

Re: Conversion/Migration tool into ReviewBoard

2010-07-14 Thread Ratnam
Thanks for the example. At least for the CVS repositories, I guess both tools seem to agree on the diff formats. In any case, preserving comments (tree style) with just the corresponding raw format diffs while migration can be a very helpful tool. As the community can understand, having a single

Re: Conversion/Migration tool into ReviewBoard

2010-07-14 Thread Christian Hammond
Hi, I agree that this would be a great tool to have. However, it's not as straightforward as it may sound. In Review Board, comments are tied to virtual lines in the diff. Rather than being tied to the line number on the left-hand file or right-hand file, it's tied to more of a row number of

Re: rb-site install - Review Board is taking a nap

2010-07-14 Thread Christian Hammond
Hi Daniel, I've been on vacation, so I'm just now reading this. The test command won't work on an installed site. It requires a development checkout. I'd recommend editing your site's conf/settings_local.py and setting DEBUG to True (note the capital 'T'). Then restart your web server and see

.reviewboardrc global placement

2010-07-14 Thread Hayes, Kyle
Does the .reviewboardrc have to be in the checkout path or can we put this in a centralized area? I ask because we have a dev environment that we are setting up and each user has an account on the system. I would rather just setup this configuration once if possible, rather than for every user.

Question regarding usage of ReviewBoard for review of arbitrary files

2010-07-14 Thread ArunBalaji
Hello, I have a requirement here where I would like to use reviewboard for reviewing files which are arbitrary. By arbitrary, I am referring to files which do not belong to any repository. But I would like to make use of ReviewBoard's features like incremental diffs etc to have a diff between an

Question about the API info

2010-07-14 Thread Vincent
Hi I am not sure that if this is a doc bug or not: http://www.reviewboard.org/docs/manual/dev/webapi/reference/apicalls/login/#api-login As you said the type of password is Boolean, which is confusing me, could you please check it? BR/Vincent -- Want to help the Review Board project? Donate

api/json/reviewrequests/{review_request_id}/diff/ not working

2010-07-14 Thread Madhavi
Hi, I need to find out files changed in a review request. I am trying to use api/json/reviewrequests/{review_request_id}/diff/. however it is returning following error. Unable to access http://punereviewsrv/trial/api/json/reviewrequests/79/diff/ (404). The host path may be invali d If I use

Re: Question about the API info

2010-07-14 Thread Christian Hammond
You're absolutely right. It should be a string. I'll fix it. A boolean would make for the worst password type ever. Christian -- Christian Hammond - chip...@chipx86.com Review Board - http://www.reviewboard.org VMware, Inc. - http://www.vmware.com On Wed, Jul 14, 2010 at 7:32 PM, Vincent

Re: api/json/reviewrequests/{review_request_id}/diff/ not working

2010-07-14 Thread Christian Hammond
Hi, Is that particular review request published? What version of Review Board are you using? Christian -- Christian Hammond - chip...@chipx86.com Review Board - http://www.reviewboard.org VMware, Inc. - http://www.vmware.com On Wed, Jul 14, 2010 at 8:28 PM, Madhavi madhavii.gu...@gmail.com

Re: Question regarding usage of ReviewBoard for review of arbitrary files

2010-07-14 Thread Christian Hammond
Hi, This is the support team, basically. David Trowbridge and I are the main developers of Review Board, and answer the support e-mails (though other people on this list are often great at jumping in with answers too). Review Board currently requires a repository for any files being viewed in

Re: api/json/reviewrequests/{review_request_id}/diff/ not working

2010-07-14 Thread Christian Hammond
This functionality doesn't exist in 1.0.x. The ability to view the list of files was added in 1.5. We're close to releasing 1.5 (we're at RC 1 and are working primarily on updating the documentation), so now would be a good time to start testing it and working on support for it. There's also a

Re: api/json/reviewrequests/{review_request_id}/diff/ not working

2010-07-14 Thread Madhavi
Great ! Thank you so much. I will download and test it. On Jul 15, 8:58 am, Christian Hammond chip...@chipx86.com wrote: This functionality doesn't exist in 1.0.x. The ability to view the list of files was added in 1.5. We're close to releasing 1.5 (we're at RC 1 and are working primarily on

Re: .reviewboardrc global placement

2010-07-14 Thread Christian Hammond
Kyle and I talked about this one-on-one, but for anyone else interested, I'll relay basically what I said. As of now, we don't have any built-in way to do site configuration. It's something I would like, but we'd have to figure out how to do it. Where does post-review look for the site

Re: Is git-svn supposed to work with --parent?

2010-07-14 Thread Christian Hammond
Hi Jared, Can you tell me if this works when using branches instead of revisions? I'm not entirely sure if git-svn works with parent branches, but I thought it did. It *should* be generating a diff between the SVN repository and the branch and sending that as a parent diff along with the

How to set p4 password in repository?

2010-07-14 Thread blanc
I try to integrate the reviewboard 1.5 rc1 to perforce. When I invoked post-review, I got the following error. -- Looking for 'localhost /reviews/' cookie in /home/test/.post-review-cookies.txt Cookie file loaded, but no cookie for this server == Review Board Login

Re: Issue 46 in reviewboard: 80-column indicator in diff view

2010-07-14 Thread reviewboard
Comment #10 on issue 46 by arunbalaji1985: 80-column indicator in diff view http://code.google.com/p/reviewboard/issues/detail?id=46 Hi, We also follow certain standards like this in our company. And we have been using review board for quite some time now. Can the review board show margin

Re: Issue 46 in reviewboard: 80-column indicator in diff view

2010-07-14 Thread reviewboard
Comment #11 on issue 46 by chipx86: 80-column indicator in diff view http://code.google.com/p/reviewboard/issues/detail?id=46 Arun, this is one of those situations where an easy solution for one group is going to cause complaints for another. In large deployments, different teams may very