Bitnami Review Board Stack-Issue while running post-review with perforce on windows

2013-07-25 Thread RB
I have set-up Bitnami Review Board stack on windows 64-bit. Later i am able to log-in to Review Board url and i was able to add a Perforce repository by clicking the Add Repository link. When i try to submit a review request for review using post-review command *post-review 12345*(changelist

Re: Can't install ReviewBoard with rb-site

2013-07-25 Thread Dirk Best
I've changed the reviewboard database to latin1 and it installs fine now (because the key is now less than 1000 bytes). Am I supposed to use latin1? --Dirk On Wednesday, July 24, 2013 1:59:29 AM UTC+2, Dirk Best wrote: MySQL works fine for a number of applications on the same server,

Re: Bitnami Review Board Stack-Issue while running post-review with perforce on windows

2013-07-25 Thread Steven MacLeod
Try changing the REPOSITORY field in your .reviewboardrc to be the name of the repository given in the RB admin panel. This is the name you give the repository when configuring it for the first time. On Thu, Jul 25, 2013 at 2:17 AM, RB lanka.a...@gmail.com wrote: I have set-up Bitnami Review

Re: Bitnami Review Board Stack-Issue while running post-review with perforce on windows

2013-07-25 Thread RB
Thanks Steven. It worked after making the changes suggested by you. On Thursday, July 25, 2013 8:26:45 PM UTC+5:30, Steven MacLeod wrote: Try changing the REPOSITORY field in your .reviewboardrc to be the name of the repository given in the RB admin panel. This is the name you give the

Re: Issue 2359 in reviewboard: Review creation fails with patches created with Subversion 1.7.x if they include a property change.

2013-07-25 Thread reviewboard
Comment #41 on issue 2359 by lrozenbl...@gmail.com: Review creation fails with patches created with Subversion 1.7.x if they include a property change. http://code.google.com/p/reviewboard/issues/detail?id=2359 Thank you! I've already started a discussion in the google group

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

2013-07-25 Thread reviewboard
Comment #7 on issue 2713 by matiso...@gmail.com: Reviewer, not author, should mark issues as resolved/reopened http://code.google.com/p/reviewboard/issues/detail?id=2713 most bug tracking tools allow reporters to close their own issues This usually can be set up in project settings.