Re: Got API Error 206 (HTTP code 400): The repository path specified is not in the list of known repositories

2012-08-21 Thread cmuser
Thanx Christian for your reply. To summarize your input- in .reviewboardrc file REPOSITORY = my repo name Where my repo name is the exact name for the repository entry in Review Board. I have done the same , but still its not working:( On Monday, August 20, 2012 10:59:53 PM UTC+5:30,

Re: Trying to configure CVS repository but always gets A repository was not found at the specified path.

2012-08-21 Thread cmuser
Hi guys, I am also facing issue in cvs connection. When i post-review from the server where reviewboard is install it works fine but from another server it fails. post here- https://groups.google.com/forum/?hl=enfromgroups=#!topic/reviewboard/VWZsG2QDreU what i did in my review board

Re: Got API Error 206 (HTTP code 400): The repository path specified is not in the list of known repositories

2012-08-21 Thread cmuser
to show more error on m/c where cvs installed , reviewboard on another m/c cat .reviewboardrc REPOSITORY = 'svn:/opt/cvsroot' REVIEWBOARD_URL = 'http://172.16.7.100:81' -bash-3.2$ post-review There was an error creating this review

Re: Got API Error 206 (HTTP code 400): The repository path specified is not in the list of known repositories

2012-08-21 Thread Christian Hammond
Oh, your RBTools is pretty old. You will need 0.4.x. 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 Tue, Aug 21, 2012 at 12:09 AM, cmuser kapilanar...@gmail.com

Re: Got API Error 206 (HTTP code 400): The repository path specified is not in the list of known repositories

2012-08-21 Thread cmuser
My gratitude again for replying Christian. Versions- ReviewBoard==1.6.1 RBTools==0.4.1 On Tuesday, August 21, 2012 12:52:17 PM UTC+5:30, Christian Hammond wrote: Oh, your RBTools is pretty old. You will need 0.4.x. What version of Review Board are you using? Christian -- Christian

Re: Got API Error 206 (HTTP code 400): The repository path specified is not in the list of known repositories

2012-08-21 Thread cmuser
I added this line in commitinfo.. /usr/bin/post-review -dn --server=http://172.16.7.100:81 --submit-as=$name --repository-url=:pserver:$user@svn:/opt/cvsroot -bash-3.2$ cvs ci -m BugID:47300 update document.txt Post-review for /opt/cvsroot/test RBTools 0.4.1 Home = / No supported

Re: post-review failing from post-commit hook, but not when run manually

2012-08-21 Thread cmuser
Hello Peter, Can you address how you fixed the same, i m getting same error. On Friday, July 13, 2012 3:20:11 AM UTC+5:30, Peter Konneker wrote: Got it. Not sure which variable it needs, though. On Wednesday, July 11, 2012 1:08:52 PM UTC-6, Peter Konneker wrote: Hey, I can run the

Re: Connect to ssh on non-standard port

2012-08-21 Thread Kristina Clair
Did you ever figure out how to get this to work? I'm having the same problem. On Friday, January 20, 2012 3:26:06 AM UTC-5, pprkut wrote: Hi! I set up reviewboard 1.6.3 and tried to add a git repository with a remote ssh location and cgit file fetching combination. I am running ssh on a

Re: Trying to configure CVS repository but always gets A repository was not found at the specified path.

2012-08-21 Thread iamagui
Paulo, Refer attached myCVS.jpg for my setting. /home/myCVS is my cvsROOT which contains the directory 'CVSROOT' and 4 modules. If your set up is similar to mine and you do NOT have access to your cvsROOT directory, then I would give the Admin username and password to the person/team who have

Re: Trying to configure CVS repository but always gets A repository was not found at the specified path.

2012-08-21 Thread iamagui
cmuser, I am not sure about REPOSITORY in .reviewboardrc but could you try just the IP for REVIEWBOARD_URL (drop the colon (:) and the port (81)), that is REVIEWBOARD_URL = http://172.16.17.100; -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/

Re: post-review failing from post-commit hook, but not when run manually

2012-08-21 Thread Peter Konneker
So first I set the path, home, and group variable and exported them from the svn hook. export PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/sbin:/usr/local/bin:/usr/X11R6/bin:/home/$AUTHOR/bin export HOME=/home/$AUTHOR export GROUP=mygroup If that doesn't work for you let me

Review entire file without a diff?

2012-08-21 Thread Paulo Silva
Hi, Besides pre and post commit reviews I also have a use case for ad-hoc reviews where the team chooses a file and code reviews it (the last revision of it). In this case I don't want to use any diff file, I just want to pick the file and be able to review it. How can I achieve this easily

Re: Review entire file without a diff?

2012-08-21 Thread Christian Hammond
Hi Paulo, Right now, your option is to submit a diff with that file as a new file. It'd then be reviewed just like any other diff. If it's going into the repository anyway, you might as well do that, since it'll be easy and familiar. Going forward, we're working on better review support for file

Re: Connect to ssh on non-standard port

2012-08-21 Thread Christian Hammond
Hi, This support doesn't yet exist in rbssh. It should be added. Would you mind filing a feature request for this? (If anyone is willing to work on a patch, it'll definitely be added sooner.) Christian -- Christian Hammond - chip...@chipx86.com Review Board - http://www.reviewboard.org VMware,

Re: Got API Error 206 (HTTP code 400): The repository path specified is not in the list of known repositories

2012-08-21 Thread Christian Hammond
You don't want to be using --repository-url, if you have a .reviewboardrc file. You also want to make sure you're running this from the checkout directory. Christian -- Christian Hammond - chip...@chipx86.com Review Board - http://www.reviewboard.org VMware, Inc. - http://www.vmware.com On

Re: Review entire file without a diff?

2012-08-21 Thread Paulo Silva
ok, I understand. Does anyone know how can I produce a diff file (CVS) with the file as a new file? On Tuesday, August 21, 2012 7:24:13 PM UTC+1, Christian Hammond wrote: Hi Paulo, Right now, your option is to submit a diff with that file as a new file. It'd then be reviewed just like

Re: Post Review is unable to upload diff

2012-08-21 Thread Rob
Thanks Shaoyan for your response. If I create a unified diff file using svn diff and then upload via post review or Review Board web UI it works fine. I have created a script that creates the unified diff, uploads via post review, and then opens the web UI. I am also looking at updating the

Can't upgrade to 1.6.11

2012-08-21 Thread Igor Berger
Hello, I'm trying to upgrade Review Board 1.6.9 to 1.6.11. I get no errors, but doesn't upgrade either (please see below). Any ideas? Thank you, Igor. root@mybox:~# easy_install -U ReviewBoard Searching for ReviewBoard Reading http://pypi.python.org/simple/ReviewBoard/ Reading

Re: Can't upgrade to 1.6.11

2012-08-21 Thread Christian Hammond
I see the upgrade of Review Board, but not the site. Make sure you follow the documentation on upgrading your Review Board site directory. Christian -- Christian Hammond - chip...@chipx86.com Review Board - http://www.reviewboard.org VMware, Inc. - http://www.vmware.com On Tue, Aug 21, 2012

Re: Issue 164 in reviewboard: Add an optional checklist for reviewers to check off

2012-08-21 Thread reviewboard
Comment #6 on issue 164 by tomasz.k...@gmail.com: Add an optional checklist for reviewers to check off http://code.google.com/p/reviewboard/issues/detail?id=164 I like this an idea with optional checklist for reviewers. We have the same problem and quality team suggest to implement this

Issue 2712 in reviewboard: [rbtools] post-review command line flag --p4-client and --p4-port does not work when P4CONFIG file is used in a multiple workspaces (perforce servers) scenario

2012-08-21 Thread reviewboard
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 2712 by qianyanj...@gmail.com: [rbtools] post-review command line flag --p4-client and --p4-port does not work when P4CONFIG file is used in a multiple workspaces (perforce servers) scenario

Issue 2713 in reviewboard: Reviewer, not author, should mark issues as resolved

2012-08-21 Thread reviewboard
Status: New Owner: Labels: Type-Enhancement Priority-Medium New issue 2713 by zk...@novadaq.com: Reviewer, not author, should mark issues as resolved http://code.google.com/p/reviewboard/issues/detail?id=2713 *NOTE: If you have a patch, please submit it to