On Thursday 23 August 2012 15:32:14 Heinz Wiesinger wrote: > Hi, > > I just tried updating to 1.6.11 and it failed with the following error: > > Rebuilding directory structure > Upgrading from version 1.6.9 > Updating database. This may take a while. > Creating tables ... > Upgrading Review Board from 1.6.9 to 1.6.11 > Project signature has changed - an evolution is required > Installing custom SQL ... > Installing indexes ... > No fixtures found. > The stored evolutions do not completely resolve all model changes. > Run `./manage.py evolve --hint` to see a suggestion for the changes > required. > > The following are the changes that could not be resolved: > In model scmtools.Repository: > Field 'extra_data' has been added > Field 'hosting_account' has been added > Error: Your models contain changes that Django Evolution cannot resolve > automatically. > > Using django-evolution 0.6.7.
I found this in an earlier thread: On Tuesday 19 June 2012 03:41:40 Christian Hammond wrote: > In the meantime, good news! There is a fix. If you can reach the Django > admin UI, go into the Database -> Django Evolutions -> Versions area and > delete the "Hinted version" you have there. Then repeat the rb-site > upgrade. That should take care of it. That indeed solved the problem for me as well. Grs, Heinz
signature.asc
Description: This is a digitally signed message part.
