That fixed it. Many Thanks!
On Friday, April 17, 2015 at 2:05:03 PM UTC-7, Christian Hammond wrote:
>
> Hi Daniel,
>
> Sorry, I've been pretty swamped.
>
> First, make a backup of your database. Then, try:
>
> DELETE FROM django_project_version WHERE id=4;
>
> Then perform the upgrade again.
Hi Daniel,
Sorry, I've been pretty swamped.
First, make a backup of your database. Then, try:
DELETE FROM django_project_version WHERE id=4;
Then perform the upgrade again.
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
Beanbag, Inc. - http
Any update here?
On Friday, March 20, 2015 at 1:29:07 PM UTC-7, Daniel Dominguez wrote:
>
> Running --hint --evolve had not been done before. It was just my
> experimenting after seeing this issue (with a current backup of the db
> first of course).
>
> Anyhow, I've attached the sql dump you re
Running --hint --evolve had not been done before. It was just my
experimenting after seeing this issue (with a current backup of the db
first of course).
Anyhow, I've attached the sql dump you requested.
Thanks!
On Friday, March 20, 2015 at 8:28:36 AM UTC-7, Daniel Dominguez wrote:
>
> When I
eanbag, Inc. - https://www.beanbaginc.com
-Original Message-
From: Daniel Dominguez
Reply: reviewboard@googlegroups.com >
Date: March 20, 2015 at 8:28:40 AM
To: reviewboard@googlegroups.com >
Subject: Problems upgrading to 2.0.13 and 2.0.15
> When I performed the upgrade form 2.0.1
When I performed the upgrade form 2.0.12 to 2.0.13, the site-upgrade
failed. It didn't seem to break our reviewboard instance, so I just
ignored it at the time. I recently upgraded to 2.0.15, and the result is
the same. Again, our reviewboard server seems to be fine, but this is
starting to
