The warnings about unapplied evolutions during rb-site install/update are
harmless. We're doing a syncdb, which Django Evolution listens to and then
checks for unapplied evolutions, but we then follow it up with an evolve.
If you're not seeing the list of fields that couldn't be evolved anymore,
y
I should also mention that the creation of RB mentioned above, also
said that it was successful...not to be a doubting Thomas,
but...ummm ...honest? Are you sure?
Here's the complete output from this segment of RB creation:
--
* Installing the site...
Build
django_evolution is reporting the version of '0.5'. This was what was
easy_install'ed.
We're trying to do the clearly-documented-as-unsupported task of
switching from SQLite3 to mysql, and at the same time, switch from RB
beta 0.8 to version 1.5, without losing any data. The new and old RBs
are
The hints are not something you should ever have to do with Review Board. In
fact, doing so can break things badly.
First, I hope you have a backup of the database, in case things go wrong.
Can you tell me what version of django-evolution is installed on that
system? You can check by doing:
I'm trying to evolve a very old database (Beta 0.8) to version 1.5,
and running into a problem. When I try the command: rb-site manage /
site/www/legacyrb evolve -- --execute
I get the message:
The stored evolutions do not completely resolve all model changes.
Run `./manage.py evol
