Hi Christian,
That worked :).
I've updated django-evolution to 0.7.3 and can confirm the upgrade went
smoothly.
Thanks a lot for your help.
Bogdan
On Friday, July 25, 2014 10:27:34 PM UTC+3, Christian Hammond wrote:
>
> Hi Bogdan,
>
> Re-running the upgrade is guaranteed to fail, because th
Hi Bogdan,
Re-running the upgrade is guaranteed to fail, because the database is in an
inconsistent state.
The problem isn’t so much an upgrade from 1.5.x to 2.0.x.. Rather, it’s
anything < 2.0 to 2.0.4.
Fortunately, I found the cause, and have put out a django-evolution 0.7.3
release. You sh
Hi Christian,
Yes I have a backup, I'm playing with it on dev server, so can reimport at
any time.
I've also tried upgrading from 1.5.3 to 1.6.22 frist (as an intermidiary
step) - this went smoothly
Next upgrading from 1.6.22 to 2.0.4 gives me the same error first, but I'm
able to rerun upgrad
Hi,
Do you have a backup of your 1.5.3 database? You’ll need one at this point,
since the new database is in an inconsistent state.
Christian
--
Christian Hammond - christ...@beanbaginc.com
Review Board - http://www.reviewboard.org
Beanbag, Inc. - http://www.beanbaginc.com
On July 24, 2014 at
Hi,
I'm having trouble upgrading existing reviewboard 1.5.3 to the new release
2.0.4.
After importing mysql dump and running rb-site upgrade I get the following
error:
CommandError: Error applying evolution: (1061, "Duplicate key name
'scmtools_repository_97c59b73'")
I tried removing index
