Reset Ship It in Review

Hi all, right now we are altering our Reviewboard installation to meet our new development requirements. In this requirements it is specified that only reviewed code is committed into our release repository (in order to achieve a safety certificate). Currently we are having the problem that in

Re: Ready VM or Recommended distribution for Review Board 1.7

On Mon, Jan 7, 2013 at 9:54 PM, Matthew Woehlke mwoehlke.fl...@gmail.com wrote: On 2013-01-07 12:20, Erik Putrycz wrote: Are there any downloadable appliances with Review Board 1.7? I found bitnami review board but they only have 1.6 In BitNami we are already working on the installers and

Post-review installation

Hi! We just managed to install Review Board on one of our organisation's web hotel (a server which we don't have direct access to), so we have a working installation and we can reach the web interface. We also learned from you that for ClearCase, post-review is not only recommended but

Re: Testing 1.7.1 on Fedora 18

Hi Stephen, Bug raised as requested.  I didn't see a place to set the CC field on the google/reviewboard bug tracker, so here's the URL so you can star it and get yourself CCed. http://code.google.com/p/reviewboard/issues/detail?id=2850 Thanks, Paul

Re: LDAP configuration problem

Well, I guess I misunderstood the meaning of the configuration field (somewhat), and found what could be a problem in the code. My LDAP server does not allow anonymous binds, and so I've had to take caution in configuring what just about every other tool calls the bind account and bind

Re: Error happens SVN HTTPS certificate not verified when adding a new repo.

Unfortunately this is a known bug in 1.7.1. We'll be putting out a 1.7.2 soon with a fix. -David On Jan 7, 2013, at 11:36 PM, Bing kevin.zhub...@gmail.com wrote: Hi, all, When I create a new repo (SVN) with https:// link, the following error message shows after click Save button.

Trouble getting custom auth backend to work

Hi All, I'm trying to setup Reviewboard(version 0.7) to authenticate with a htpasswd file. Followed the instructions here, http://www.reviewboard.org/docs/codebase/dev/extending/auth-backends/ and got to the point where my backend started appearing in the Authentication dropdown from Admin

Re: Error happens SVN HTTPS certificate not verified when adding a new repo.

Hi all, I am also facing this issue on 1.7.1. Both buttons are disabled the error log says Server certificate verification failed: issuer is not trusted. The data directory is owned by apache2 user. I am using apache+ mod_wsgi. It will be a great help if somebody can suggest a solution.

Re: Cannot add a remote SVN repo on 1.6.15 (Regression?)

I'd be happy to do some code-level digging. Any tips on where to start? Thanks Liam -- 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/ -~--~~~~--~~--~--~---

rb-site upgrade fails on database migration

We've been making regular backups of our RB 1.5.5 database, and I decided it was time to verify that we can restore the DB to a new install in case our server fails. The backups are made with mysqlhotcopy, so I understand they can be restored by simply stopping the mysql service, copying the

Recent upgrade to 1.7.1 broke my site.

Hi, Today, I upgraded my review board installation to 1.7.1. By doing this, My site is broken. I get internal server error. In the apache log file, I see the following lines. [Tue Jan 08 14:55:08 2013] [notice] Apache/2.2.14 (Ubuntu) Phusion_Passenger/2.2.7 PHP/5.3.2-1ubuntu4.17 with

Re: Recent upgrade to 1.7.1 broke my site.

DeprecationWarnings are harmless. There's probably something else (either in the apache log or the reviewboard log). -David On Tue, Jan 8, 2013 at 3:01 PM, Custom Apps sme...@customapps.in wrote: Hi, Today, I upgraded my review board installation to 1.7.1. By doing this, My site is

Re: Recent upgrade to 1.7.1 broke my site.

I am not an expert in this. So not sure what else to look for. Even though they are deprecationwarning, they seem to have error tag. Can this be an issue? The apache log also has these entries. [Tue Jan 08 23:04:46 2013] [error] import md5

Re: Recent upgrade to 1.7.1 broke my site.

OK. My bad. Somehow I upgraded the wrong site. So the database was not upgraded and the error was coming of missing db tables. Doing rb-site upgrade for the correct host fixed this. Sorry for this. Thanks On Tuesday, January 8, 2013 3:03:47 PM UTC-8, David Trowbridge wrote:

Re: Error happens SVN HTTPS certificate not verified when adding a new repo.

I've worked around this issue: 1. login the server, run svn list https://. 2. accept the certificate permanently. 3. then copy files generated in ~/.subversion/auth/svn.simple(server) to /var/www/reviewboard(your site name)/data/.subversion/auth/svn.xxx 4. change the file/group

Re: Issue 2723 in reviewboard: Show issue status in dashboard

Comment #5 on issue 2723 by matthew@kitware.com: Show issue status in dashboard http://code.google.com/p/reviewboard/issues/detail?id=2723 Just showing unresolved issues would be a significant improvement. Three column choices for unresolved, resolved, and total (or five, adding also

Re: Issue 2851 in reviewboard: Error: The patch to 'ProcessCVSFiles.java' didn't apply cleanly

Updates: Status: NeedInfo Comment #1 on issue 2851 by trowb...@gmail.com: Error: The patch to 'ProcessCVSFiles.java' didn't apply cleanly http://code.google.com/p/reviewboard/issues/detail?id=2851 How did you create your diff? What is in those .rej files? -- You received this

Re: Issue 658 in reviewboard: Error : The patch to 'filepath' didn't apply cleanly.

Comment #16 on issue 658 by trowb...@gmail.com: Error : The patch to 'filepath' didn't apply cleanly. http://code.google.com/p/reviewboard/issues/detail?id=658 Getting rejects usually indicates some problem with how the diff was generated. Check the .rej file to see what failed. -- You

Re: Issue 2833 in reviewboard: post-review needs to override git diff.renames option

Comment #2 on issue 2833 by matthew@kitware.com: post-review needs to override git diff.renames option http://code.google.com/p/reviewboard/issues/detail?id=2833 This is fixed as of bacdab01f33; can someone with adequate permissions please close? -- You received this message because

Re: Issue 2833 in reviewboard: post-review needs to override git diff.renames option

Updates: Status: Fixed Comment #3 on issue 2833 by trowb...@gmail.com: post-review needs to override git diff.renames option http://code.google.com/p/reviewboard/issues/detail?id=2833 (No comment was entered for this change.) -- You received this message because you are subscribed

Issue 2853 in reviewboard: Reviewer should be able to reopen issues

Status: New Owner: Labels: Type-Enhancement Priority-Medium New issue 2853 by brunon...@brunonery.com: Reviewer should be able to reopen issues http://code.google.com/p/reviewboard/issues/detail?id=2853 What version are you running? 1.7.1 What's the URL of the page this enhancement

Issue 2854 in reviewboard: Reviewer should be able to close issues

Status: New Owner: Labels: Type-Enhancement Priority-Medium New issue 2854 by brunon...@brunonery.com: Reviewer should be able to close issues http://code.google.com/p/reviewboard/issues/detail?id=2854 What version are you running? 1.7.1 What's the URL of the page this enhancement

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

Updates: Summary: Reviewer, not author, should mark issues as resolved/reopened Comment #2 on issue 2713 by trowb...@gmail.com: Reviewer, not author, should mark issues as resolved/reopened http://code.google.com/p/reviewboard/issues/detail?id=2713 (No comment was entered for this

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

Comment #3 on issue 2713 by trowb...@gmail.com: Reviewer, not author, should mark issues as resolved/reopened http://code.google.com/p/reviewboard/issues/detail?id=2713 Issue 2853 has been merged into this issue. -- You received this message because you are subscribed to the Google Groups

Re: Issue 2853 in reviewboard: Reviewer should be able to reopen issues

Updates: Status: Duplicate Mergedinto: 2713 Comment #1 on issue 2853 by trowb...@gmail.com: Reviewer should be able to reopen issues http://code.google.com/p/reviewboard/issues/detail?id=2853 (No comment was entered for this change.) -- You received this message because you

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

Comment #4 on issue 2713 by trowb...@gmail.com: Reviewer, not author, should mark issues as resolved/reopened http://code.google.com/p/reviewboard/issues/detail?id=2713 Issue 2854 has been merged into this issue. -- You received this message because you are subscribed to the Google Groups

Re: Issue 2854 in reviewboard: Reviewer should be able to close issues

Updates: Status: Duplicate Mergedinto: 2713 Comment #1 on issue 2854 by trowb...@gmail.com: Reviewer should be able to close issues http://code.google.com/p/reviewboard/issues/detail?id=2854 (No comment was entered for this change.) -- You received this message because you

Re: Issue 2238 in reviewboard: unicode error in postreview

Updates: Status: Fixed Comment #5 on issue 2238 by trowb...@gmail.com: unicode error in postreview http://code.google.com/p/reviewboard/issues/detail?id=2238 Pushed the fix to rbtools master (7b53c05). Thanks! -- You received this message because you are subscribed to the Google Groups

Issue 2855 in reviewboard: Clicking into an issue on the summary doesn't focus on the issue

Status: New Owner: Labels: Type-Defect Priority-Medium New issue 2855 by brunon...@brunonery.com: Clicking into an issue on the summary doesn't focus on the issue http://code.google.com/p/reviewboard/issues/detail?id=2855 What version are you running? 1.7.1 What's the URL of the page

Re: Issue 2856 in reviewboard: Error in accessing the review link

Updates: Status: Invalid Comment #1 on issue 2856 by trowb...@gmail.com: Error in accessing the review link http://code.google.com/p/reviewboard/issues/detail?id=2856 You need to fill out the form. If you're able to provide the requested information, please add a comment and we'll