Re: Database upgrade from 1.7.27 to 2.5.2

Hi, Looks like you have a mix of InnoDB and MyISAM tables. You're going to need to update all tables in your database to use InnoDB (or configure MySQL to use MyISAM by default, though InnoDB is preferable). The workaround you have that results in the "attachment_histories" bit is due to

Re: [Testing Needed] Review Board 2.5.2 for RHEL/CentOS 7

On Mon, Dec 7, 2015 at 11:21 AM Stephen Gallagher wrote: > Hmm, I thought I fixed that version. I'll push an update immediately. If > you manually run `yum update python-django-evolution > --enablerepo=epel-testing` and then attempt the upgrade, does that resolve >

Re: [Testing Needed] Review Board 2.5.2 for RHEL/CentOS 7

On Sat, Dec 5, 2015 at 10:29 AM Paul Fee wrote: > Hi Stephen, > > That's great news, I had been wondering if Fedora/RHEL users would be > seeing RB2.5 soon. > > On Fedora, it looks like the Django packages have moved ahead to 1.8, but > RB still needs 1.6. Hence

Re: [Testing Needed] Review Board 2.5.2 for RHEL/CentOS 7

Hmm, I thought I fixed that version. I'll push an update immediately. If you manually run `yum update python-django-evolution --enablerepo=epel-testing` and then attempt the upgrade, does that resolve your upgrade issue? What version of django-evolution do you have right now? 0.7.5? On Mon, Dec

Re: [Testing Needed] Review Board 2.5.2 for RHEL/CentOS 7

Hello Stephen, I've been patiently waiting for this for weeks now. Glad to see it's getting close. Some issues I found upgrading from EPEL 2.0.18: The RPM requires: python-django-evolution >= 0.7.1 ReviewBoard requires: django-evolution>=0.7.6,<=0.7.999 *and during the rb-site upgrade I get

Re: GitLab hosting stopped working

Hi Ian, Can you verify that the username associated with those repositories still has the necessary access permissions on the GitLab server? I checked the code in question, involving repository verification and how credentials are used, and it hasn't changed since 2.0.x, so at this point I'd

Re: Database upgrade from 1.7.27 to 2.5.2

Some additional information after further experimentation: * I tried upgrading from the same 1.7.27 database to 2.0.18. This worked perfectly fine. I ran compressdiffs afterwards as suggested, that worked too. * I then tried upgrading from 2.0.18 to 2.5.2, but got the same "Can't create table

RBTools 0.7.4 error 105 POSTing a diff

I am doing some development which is tracked by XML files. It looks like these XML files are breaking RBTools (java files post file). I get a 105 error stating path is not found. Not really sure what this means. But I strongly suspect its due to parsing of the diff. Attached is said diff

RBtools 0.7.4 error 105 path not found.

Sorry if this is a double post. Getting error with some files posting using RBTools. Java files seem to work fine. I use something called Mirth Connect which generates XML files as code. Basically when RBT tries to upload the diff it fails with the 105 error. Attached is the diff. --

Database upgrade from 1.7.27 to 2.5.2

I'm attempting to migrate an existing ReviewBoard database from 1.7.27 to 2.5.2, on a CentOS 7.1 system using sgallagher's RPMs. The error looks like a permission problem, but on same system, I am able to create a new site with "rb-site install" and it works nicely. I then dropped dropped the

Re: RBtools 0.7.4 error 105 path not found.

What version of Review Board? What version control system (and version thereof)? Is there anything in the server log? -David On Mon, Dec 7, 2015 at 11:43 AM Rob Dejournett wrote: > Sorry if this is a double post. Getting error with some files posting > using RBTools.

Re: Database upgrade from 1.7.27 to 2.5.2

Did you run this with the recent django-evolution 0.7.6 update? That specifically addresses some upgrade issues unique to MySQL. On Mon, Dec 7, 2015, 9:40 PM rfs wrote: > Some additional information after further experimentation: > > * I tried upgrading from the same 1.7.27