@googlegroups.com
Date: May 29, 2015 at 7:06:37 AM
To: reviewboard@googlegroups.com reviewboard@googlegroups.com
Subject: Re: RB migrate and upgrade from 1.6.16 to 2.0.15
Thanks Christian, that solved it. Have the new version on running in
parallel now as a hot standby on another node from the 1.6
Hi Christian,
Tried it there on new install, import d/b and then the upgrade. Before
upgrade ID 7 existed just as you say, and after the upgrade 8 exists.
Output looks similar in error to the original run. Would any further d/b
dumps assist you here?
# rb-site upgrade site
Rebuilding
Hey John,
Sorry, haven't had time until now.
So first, back up your database. I then want you to try this:
DELETE FROM django_project_version WHERE id IN (7, 8);
There's an issue that's come up a couple of times in django-evolution,
which I have not been able to trace, where two entries
reviewboard@googlegroups.com
Subject: Re: RB migrate and upgrade from 1.6.16 to 2.0.15
Hi Christian,
Tried it there on new install, import d/b and then the upgrade. Before
upgrade ID 7 existed just as you say, and after the upgrade 8 exists.
Output looks similar in error to the original run
Hi Christian,
Any pointers on this problem?
Thanks,
John
On Thursday, 21 May 2015 16:29:27 UTC+1, John McGowan wrote:
Hi,
I've been trying to upgrade a RB instance that got to 1.6.16 to 2.0.15 on
another node (RH6.3 vs RH6.6).
I've the prereq packages on:
# pip freeze
Hi,
I've been trying to upgrade a RB instance that got to 1.6.16 to 2.0.15 on
another node (RH6.3 vs RH6.6).
I've the prereq packages on:
# pip freeze
Beaker==1.3.1
cas==0.15
cups==1.0
cupshelpers==1.0
decorator==3.0.1
Django==1.6.11
django-evolution==0.7.5
django-haystack==2.3.1
Hi John,
This looks like some state is a bit messed up in the database for the
evolution history. Can you attach an SQL dump of the contents of the
django_project_version and django_evolution tables?
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org