Re: Upgrading Review Board 1.7.6 to 2.0.2

David, How would I go about doing that? I'm new to python why I went the route that I did. -Robert On Monday, October 19, 2015 at 2:29:03 PM UTC-6, David Trowbridge wrote: > > > On Mon, Oct 19, 2015 at 1:25 PM, Robert Bolen > wrote: > >> 'Mantis User Database' > > > This is not part of the ups

Any success upgrading RHEL 6, Centos 6, or Fedora 15- from ReviewBoard 1.7.x to 2.0.20

Hey I am wondering if there are any success stories for this upgrade on older versions of these os'. I have a Fedora 15 vm and am wondering if it is worth it to try this upgrade or move to a newer vm altogether. Thanks. -- Supercharge your Review Board with Power Pack: https://www.reviewboard.

Re: Any success upgrading RHEL 6, Centos 6, or Fedora 15- from ReviewBoard 1.7.x to 2.0.20

I'd personally recommend moving to a CentOS 7 host and my EPEL 7 RPMs, which has 2.0.x today and will have 2.5.x once it's released. On Tue, Oct 20, 2015 at 12:46 PM Chris Lang wrote: > Hey I am wondering if there are any success stories for this upgrade on > older versions of these os'. > I have

Re: Upgrading Review Board 1.7.6 to 2.0.2

Robert, You can either do it as part of an extension, or just using entry points. See https://www.reviewboard.org/docs/manual/2.0/extending/auth-backends/#packaging -David On Tue, Oct 20, 2015 at 9:15 AM, Robert Bolen wrote: > David, > > How would I go about doing that? I'm new to python why I

Review Board 2.0.2: ValueError at /: dictionary update sequence element #0 has length 1; 2 is required

I have upgraded from Review Board 1.7.6 to 2.0.2, I did not make any changes to the urls.py file and I still getting the following error message: Request Method: GET Request URL: http://10.73.201.116/ Django Version: 1.6.11 Exception Type: ValueError Exception Value: dictionary update sequenc

Re: Review Board 2.0.2: ValueError at /: dictionary update sequence element #0 has length 1; 2 is required

Since you are making changes to the Review Board code, it is basically impossible for us to debug your issues with just a traceback. If you want help, you'll need to attach a diff of all your changes. As I mentioned in my previous e-mail, I highly recommend adding authentication backends as part o

Re: How to do not allow to close review if issue still open?

Any recommendation? On Tuesday, October 20, 2015 at 5:11:27 PM UTC+11, MoonWalker wrote: > > Is it possible to do not allow to close any review if 1+ issues still > open? BTW I am using RB 2.0.20 > > Cheers > -- Supercharge your Review Board with Power Pack: https://www.reviewboard.org/powerpa