Christian, your tip works great $ rb-site manage /var/www/reviews.example.info shell >>> from django_evolution.models import Version >>> Version.objects.exclude(evolutions__pk__gt=0).delete() >>> quit()
$ rb-site upgrade /var/www/reviews. <http://reviews.onesys.info><http://reviews.onesys.info> example <http://reviews.example.info>.info [...] ------------------ <begin log output> ------------------ Creating tables ... There are unapplied evolutions for accounts. There are unapplied evolutions for diffviewer. There are unapplied evolutions for reviews. Adding baseline version for new models Project signature has changed - an evolution is required Installing custom SQL ... Installing indexes ... Installed 0 object(s) from 0 fixture(s) *Evolution successful*. ------------------- <end log output> ------------------- "And I said to myself : « what a wonderful world" ! Thanks for your help Chris Le mardi 22 janvier 2013 23:30:39 UTC+1, Christian Hammond a écrit :Hi, Sorry to hear you got bit by some failed upgrade problem. All upgrades *should* be done in one transaction. It's *possible* that this is really a problem of some upgrade metadata that is screwed up. Something to try is: $ rb-site manage /path/to/site shell >>> from django_evolution.models import Version >>> Version.objects.exclude(evolutions__pk__gt=0).delete() Back up the database first, though. Once you run that, try to do an upgrade again. Christian -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~----------~----~----~----~------~----~------~--~--- To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en
