Hi Tucker, (Is j...@gmail.com really your e-mail address?)
This is something I've seen a few times now and still haven't figured out the cause of. Can I have you answer the questions in this bug report: http://code.google.com/p/reviewboard/issues/detail?id=2186 It'll help us figure out what's causing this. Christian -- Christian Hammond - chip...@chipx86.com Review Board - http://www.reviewboard.org VMware, Inc. - http://www.vmware.com On Tue, Jul 26, 2011 at 1:22 PM, Tucker <j...@gmail.com> wrote: > Attempted an upgrade from RC1 to RC2. > > 1. easy_install -U ReviewBoard > 2. easy_install -U RBTools > 3. rb-site upgrade /var/www/sites/reviews-dev.zynga.com/ > > And this is where it broke: > > # rb-site upgrade /var/www/sites/reviews-dev.zynga.com/ > Rebuilding directory structure > Updating database. This may take a while. > Creating tables ... > There are unapplied evolutions for diffviewer. > Project signature has changed - an evolution is required > Installing custom SQL ... > Installing indexes ... > No fixtures found. > > /usr/lib/python2.4/site-packages/pycrypto-2.3-py2.4-linux-x86_64.egg/Crypto/Util/randpool.py:40: > RandomPool_DeprecationWarning: This application uses RandomPool, which > is BROKEN in older releases. See > http://www.pycrypto.org/randpool-broken > Unable to load SCMTool perforce = > reviewboard.scmtools.perforce:PerforceTool: invalid syntax > (perforce.py, line 155) > 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 reviews.ReviewRequest: > Field 'inactive_file_attachments' has been added > Field 'file_attachments' has been added > In model reviews.Review: > Field 'file_attachment_comments' has been added > In model reviews.ReviewRequestDraft: > Field 'inactive_file_attachments' has been added > Field 'file_attachments' has been added > In model accounts.Profile: > Field 'is_private' has been added > Error: Your models contain changes that Django Evolution cannot > resolve automatically. > > I haven't run the evolve script at all, which was a question I saw > come up in a similar thread. The host is running CentOS 5.2 and > python2.4. This machine was originally running beta1 and was then > upgraded to RC1, without a problem. It is a dev host, so there's a > possibility that something was done to the machine that was unrelated > but had an impact. > > -- > > --tucker > > -- > 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 -- 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
