Christian,
Is it possible for me to make manual changes to the database that would
allow this operation to complete? If I understood more about what the error
is describing, I might be able to make some direct changes to work around
it.
-Chris
On Monday, April 8, 2013 2:45:23 PM UTC-4, Chris
Hi Chris,
That looks like it's trying to re-add a very, very old field that you
absolutely already have. So something is clearly quite wrong.
Can you run that with evolve --hint (no --execute) and paste the results to
me?
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board -
~# rb-site manage /var/lib/reviewboard evolve -- --hint
#- Evolution for auth
from django_evolution.mutations import DeleteModel
MUTATIONS = [
DeleteModel('Message')
]
#--
#- Evolution for accounts
from django_evolution.mutations import AddField
from django.db
I attempted to perfom an upgrade of one of our ReviewBoard installations
and I have run into a problem. The first server upgraded fine, but this one
is not working. I folloed some of the recommendations in another post, but
I was not successful. Thank you for any help you can provide.
~$
0.6.7-py2.6
On Monday, April 8, 2013 1:46:57 PM UTC-4, Christian Hammond wrote:
Hi Chris,
What version of the django_evolution module is installed?
Christian
--
Christian Hammond - chi...@chipx86.com javascript:
Review Board - http://www.reviewboard.org
Beanbag, Inc. -
Try upgrading to 0.6.9. There were a lot of fixes that went in since your
version.
Christian
On Apr 8, 2013, at 10:53, Chris Eagan cea...@gmail.com wrote:
0.6.7-py2.6
On Monday, April 8, 2013 1:46:57 PM UTC-4, Christian Hammond wrote:
Hi Chris,
What version of the django_evolution
I think my last answer was wrong. I tried to upgrade and got this:
~# easy_install -U django_evolution
Searching for django-evolution
Reading http://downloads.reviewboard.org/releases/ReviewBoard/1.6/
Reading http://pypi.python.org/simple/django_evolution/
Reading
When you mentioned different servers, were these each with their own database?
It's complaining about fields that already existed in 1.6.11, which shouldn't
be correct. It's also showing that those evolutions were already applied.
At any point did you ever downgrade or wipe an evolution?
Yes, each server used it's own independent database. They exist on fully
distinct virtual machines.
This is only the second time this server has been upgraded. The first
upgrade attempt I did today was run with the older version of
django_evolution. That might be why the upgrade wasn't
Sorry about that.. We hit some rough bugs in Django Evolution (or rather,
introduced scenarios it wasn't prepared for), but I do think that going
forward, these issues should be mostly gone.
So I don't normally advise this, but here's what I'd recommend in this case:
1) Back up your database
2)
10 matches
Mail list logo
