I did not back up the database, since I was doing this to an old server I no longer care about. If I wait, will upgrading to 2.0.2 when it's released get me past this?
Thanks! On Thursday, June 12, 2014 4:28:44 PM UTC-7, Christian Hammond wrote: > > Sorry, this is due to a change we made in 1.7.26 that hasn’t been > reflected in 2.0.2 yet. > > We’re going to try to get a release out tonight or tomorrow of 2.0.2. > > Did you back up the database? Can you stay on 1.7.26 for now? > > Christian > > -- > Christian Hammond - [email protected] <javascript:> > Review Board - http://www.reviewboard.org > Beanbag, Inc. - http://www.beanbaginc.com > > On June 12, 2014 at 4:27:14 PM, Brian ([email protected] <javascript:>) > wrote: > > I have run into an issue upgrading from 1.7.26 to 2.0.1. > > I did > > easy_install -U Reviewboard > > rb-site upgrade /path/to/site > > and got: > Rebuilding directory structure > Updating database. This may take a while. > > The log output below, including warnings and errors, > can be ignored unless upgrade fails. > > ------------------ <begin log output> ------------------ > Creating tables ... > There are unapplied evolutions for auth. > There are unapplied evolutions for contenttypes. > There are unapplied evolutions for accounts. > There are unapplied evolutions for attachments. > There are unapplied evolutions for changedescs. > There are unapplied evolutions for diffviewer. > There are unapplied evolutions for hostingsvcs. > There are unapplied evolutions for reviews. > There are unapplied evolutions for scmtools. > Project signature has changed - an evolution is required > Installing custom SQL ... > Installing indexes ... > Installed 0 object(s) from 0 fixture(s) > 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: > The application markup has been deleted > In model accounts.Profile: > Field 'should_send_email' has been deleted > CommandError: Your models contain changes that Django Evolution cannot > resolve automatically. > > > I had not noticed the need for an update Django until after I did this, so > maybe that has thrown something off, but I did make sure Django and > django_evolution were both up to date and tried again with the same result. > > Is this install just toast now? > > Thanks, > Brian > -- > Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ > --- > Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ > --- > Happy user? Let us know at http://www.reviewboard.org/users/ > --- > You received this message because you are subscribed to the Google Groups > "reviewboard" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] <javascript:>. > For more options, visit https://groups.google.com/d/optout. > > -- Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ --- Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ --- Happy user? Let us know at http://www.reviewboard.org/users/ --- You received this message because you are subscribed to the Google Groups "reviewboard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
