Re: Review groups and private repositories

Ah, now it makes sense. Thanks! On Wednesday, 13 November 2013 22:36:21 UTC+2, Christian Hammond wrote: If a user is on group1 but not group2, and a change is posted to group2, then the user will not be allowed to see the change. The reason is that there may be discussions from members on

Re: A repository was not found at the specified path.

Christian, barry@R0150313:~/cvs/repo$ cvs -f -d :pserver:m022927@R0199562:/QREADS5_1_repo checkout -r HEAD -p CVSROOT/modules cvs server: User m022927 cannot read CVSROOT on tag/branch HEAD Looking forward to your comments... Thanks, Barry On Friday, November 8, 2013 11:23:48 AM UTC-6, Barry

Ways to speed up 1.6.15 to 1.7.18 upgrade

Anyone have ideas on how to speed up the upgrade from 1.6.15 to 1.7.18 or more specifically the evolutions involved? When tested on a snapshot of Review Board database it appeared to take almost 4 hours to process the diffviewer_filediff table and around 90 minutes for the

Re: A repository was not found at the specified path.

In this case, your path isn't correct. It should be your CVSROOT path, which tends to end with :/cvsroot or similar. I don't know if that's it on yours or not, but you'll need to investigate it. What does it say in a local checkout when you cat CVS/Root? Christian -- Christian Hammond -

Re: A repository was not found at the specified path.

barry@R0150313:~/cvs/repo/QReadsApp$ cvs -d :pserver:m022927@R0199562:/QREADS5_1_repo checkout QReadsApp cvs server: Updating QReadsApp U QReadsApp/.classpath U QReadsApp/.cvsignore U QReadsApp/.project U QReadsApp/.runtime U QReadsApp/ORBackup.properties . . . U

Re: Change in LDAP authentication behavior in 1.7.14 breaks environments that don't allow anonymous searches

David, Sorry for the massive delay! I've finally posted it at https://reviews.reviewboard.org/r/4953/. On Friday, October 18, 2013 1:51:59 AM UTC-7, David Trowbridge wrote: Daniel, I'd suggest making a quick clone of the reviewboard repository, making your change, and then posting your

Issue 3138 in reviewboard: Implied reviewers don't get review notification email when it is created initially

Status: New Owner: Labels: Type-Defect Priority-Medium New issue 3138 by eyuw...@gmail.com: Implied reviewers don't get review notification email when it is created initially http://code.google.com/p/reviewboard/issues/detail?id=3138 What version are you running? 1.7.6 What's the URL

Re: Issue 3138 in reviewboard: Implied reviewers don't get review notification email when it is created initially

Updates: Status: NeedInfo Comment #1 on issue 3138 by chip...@gmail.com: Implied reviewers don't get review notification email when it is created initially http://code.google.com/p/reviewboard/issues/detail?id=3138 This is strange. Unless there's a bug in 1.7.6 (which I don't