Re: Reviewboard upgrade failure

On Fri, Jan 15, 2016 at 11:04 PM, Christian Hammond wrote: > Hi Ben, > > This is due to a mismatch between MySQL table types. The existing tables are > likely MyISAM, with MySQL now defaulting to InnoDB for new ones. You'll need > to either migrate all the existing

Re: rb-site upgrade error: Your models contain changes that Django Evolution cannot resolve automatically

Hi Jasper, This definitely looks to be due to custom model changes made by someone there. You'll need to do some special stuff to disentangle these. You definitely don't want to use --hint --execute is a recipe for disaster (got a backup?). What you're going to have to do is take those old model

Getting "The file ...... could not be found in the repository" with mercurial repository confugured with ssh

I am using Review Board 2.0.7 with mercurial repository configured with ssh. I created a new review request and uploaded the diff and parent diff for a committed changeset. But I get the following error: There was an error displaying this diff. The file

Re: Reviewboard upgrade failure

Hi Ben, You'll have a much easier time restoring from a backup. It's hard to say how far it went through the evolution process, and unfortunately today it doesn't keep track of how far it got and what it'd have to do to recover. You'd have a lot of trial and error to fix it manually. You can try

Re: Getting "The file ...... could not be found in the repository" with mercurial repository confugured with ssh

2.0.7 is pretty old at this point. Is it possible to see if this still fails with the latest 2.0.x release? -David On Fri, Jan 15, 2016 at 8:04 AM Ashutosh Naik wrote: > I am using Review Board 2.0.7 with mercurial repository configured with > ssh. I created a new

Re: Reviewboard upgrade failure

On Sat, Jan 16, 2016 at 6:09 AM, Christian Hammond wrote: > Hi Ben, > > You'll have a much easier time restoring from a backup. It's hard to say how > far it went through the evolution process, and unfortunately today it > doesn't keep track of how far it got and what it'd

Re: rb-site upgrade error: Your models contain changes that Django Evolution cannot resolve automatically

Thanks for the feedback Christian I actually managed to get further by even smaller increments. 1.7.1 -> 1.7.2 ->1.7.28 and finally 2.0 The process is slow and i have to resolve things like Djblet needs to be updated, importlib missing etc so it seems to be working so far - why is

Re: Reviewboard upgrade failure

Hi Ben, This is due to a mismatch between MySQL table types. The existing tables are likely MyISAM, with MySQL now defaulting to InnoDB for new ones. You'll need to either migrate all the existing tables, or tell MySQL to use the existing type for new tables. (It's a pretty terrible error, but