Hi, I got the same or similar problem when upgrading reviewboard site ( rb-site upgrade ) from 1.6.7.1 to 1.6.9.
easy_install worked OK, but it was rb-site upgrade that failed: # easy_install -U ReviewBoard Searching for ReviewBoard Reading http://pypi.python.org/simple/ReviewBoard/ Reading http://www.reviewboard.org/ Reading http://downloads.reviewboard.org/releases/ReviewBoard/1.5/ Reading http://downloads.reviewboard.org/releases/ReviewBoard/1.6/ Reading http://www.review-board.org/ Reading http://downloads.review-board.org/releases/ReviewBoard/1.0/ Reading http://downloads.review-board.org/releases/ Best match: ReviewBoard 1.6.9 Downloading http://downloads.reviewboard.org/releases/ReviewBoard/1.6/ReviewBoard-1.6.9-py2.7.egg Processing ReviewBoard-1.6.9-py2.7.egg creating /usr/local/lib/python2.7/dist-packages/ReviewBoard-1.6.9-py2.7.egg Extracting ReviewBoard-1.6.9-py2.7.egg to /usr/local/lib/python2.7/dist-packages Removing ReviewBoard 1.6.7.1 from easy-install.pth file Adding ReviewBoard 1.6.9 to easy-install.pth file Installing rb-site script to /usr/local/bin Installing rbssh script to /usr/local/bin Installed /usr/local/lib/python2.7/dist-packages/ReviewBoard-1.6.9-py2.7.egg Reading http://downloads.reviewboard.org/mirror/ Processing dependencies for ReviewBoard Searching for Djblets==0.6.19 Reading http://pypi.python.org/simple/Djblets/ Reading http://www.review-board.org/wiki/Djblets Reading http://downloads.review-board.org/releases/Djblets/0.6/ Reading http://www.reviewboard.org/wiki/Djblets Reading http://downloads.review-board.org/releases/Djblets/0.5/ Best match: Djblets 0.6.19 Downloading http://downloads.reviewboard.org/releases/Djblets/0.6/Djblets-0.6.19-py2.7.egg Processing Djblets-0.6.19-py2.7.egg creating /usr/local/lib/python2.7/dist-packages/Djblets-0.6.19-py2.7.egg Extracting Djblets-0.6.19-py2.7.egg to /usr/local/lib/python2.7/dist-packages Removing Djblets 0.6.18 from easy-install.pth file Adding Djblets 0.6.19 to easy-install.pth file # rb-site upgrade /var/www/reviews.aas.priv/ Rebuilding directory structure Updating database. This may take a while. Creating tables ... Upgrading Review Board from 1.6.7.1 to 1.6.9 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. Thus for now, I have not restarted apache or memcached, and the reviewboard website still says 1.6.7.1 One thing that happened before the upgrade of reviewboard ( before easy_install -U ReviewBoard ) was that mysql was updated via apt-get: >From /var/log/apt/history.log: Start-Date: 2012-06-15 14:44:20 Commandline: apt-get upgrade -V Upgrade: mysql-server:amd64 (5.1.62-0ubuntu0.11.10.1, 5.1.63-0ubuntu0.11.10.1), libapparmor-perl:amd64 (2.7.0~beta1+bzr1774-1ubuntu2, 2.7.0~beta1+bzr1774-1ubuntu2.1), libmysqlclient-dev:amd64 (5.1.62-0ubuntu0.11.10.1, 5.1.63-0ubuntu0.11.10.1), mysql-server-core-5.1:amd64 (5.1.62-0ubuntu0.11.10.1, 5.1.63-0ubuntu0.11.10.1), libmysqlclient16:amd64 (5.1.62-0ubuntu0.11.10.1, 5.1.63-0ubuntu0.11.10.1), mysql-client-core-5.1:amd64 (5.1.62-0ubuntu0.11.10.1, 5.1.63-0ubuntu0.11.10.1), mysql-client:amd64 (5.1.62-0ubuntu0.11.10.1, 5.1.63-0ubuntu0.11.10.1), linux-tools-common:amd64 (3.0.0-20.34, 3.0.0-21.35), linux-libc-dev:amd64 (3.0.0-20.34, 3.0.0-21.35), mysql-common:amd64 (5.1.62-0ubuntu0.11.10.1, 5.1.63-0ubuntu0.11.10.1), mysql-server-5.1:amd64 (5.1.62-0ubuntu0.11.10.1, 5.1.63-0ubuntu0.11.10.1), mysql-client-5.1:amd64 (5.1.62-0ubuntu0.11.10.1, 5.1.63-0ubuntu0.11.10.1) End-Date: 2012-06-15 14:45:11 Regards, John On Tuesday, 12 June 2012 18:14:46 UTC+10, Antti Paajoki wrote: > > Hi, > > We've been happily running reviewboard for some time and now tried to > upgrade from 1.6.4.1 to 1.6.8. > Unfortunately, it was not a immediate success. > > Reviewboard upgrade with easy_install goes without errors, but the site > upgrade fails during Django Evolution. > > [start of log] > > $ rb-site upgrade /path/to/reviewboard > Rebuilding directory structure > Updating database. This may take a while. > /usr/local/lib/python2.6/dist-packages/Django-1.3.1-py2.6.egg/django/db/__init__.py:60: > > DeprecationWarning: Short names for ENGINE in database configurations are > deprecated. Prepend default.ENGINE with 'django.db.backends.' > DeprecationWarning > Creating tables ... > Creating table hostingsvcs_hostingserviceaccount > Upgrading Review Board from 1.6.4.1 to 1.6.8 > There are unapplied evolutions for scmtools. > Adding baseline version for new models > Project signature has changed - an evolution is required > Installing custom SQL ... > Installing indexes ... > No fixtures found. > /usr/local/lib/python2.6/dist-packages/pycrypto-2.3-py2.6-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 > RandomPool_DeprecationWarning) > 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.Comment: > Field 'issue_opened' has been added > Field 'issue_status' has been added > In model reviews.Review: > Field 'file_attachment_comments' has been added > In model reviews.ReviewRequest: > Field 'inactive_file_attachments' has been added > Field 'file_attachments' has been added > In model reviews.ScreenshotComment: > Field 'issue_opened' has been added > Field 'issue_status' 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. > > [end of log] > > Running `./manage.py evolve --hint` from the .egg/reviewboard directory > yields: > 'Unable to import settings_local.py: No module named settings_local' > > The file settings_local.py is at the reviewboard site directory, and > symlinking it under .egg/reviewboard/ changes the result so that the > `./manage.py evolve --hint` seems to run correctly. However, rb-site > upgrade does work any better. > > Apparently running the evolution manually with parameters '--hint > --execute' would be a Really Bad Idea, so I did not try that. > > So it would seem that the problem would be related to the upgrade script > being unable to locate the settings_local.py correctly, but I can't > pinpoint where the problem lies. Any ideas? > > Environment details: > Linux 2.6.32-21-server #32-Ubuntu SMP Fri Apr 16 09:17:34 UTC 2010 x86_64 > GNU/Linux Ubuntu 10.04.4 LTS > Running the following versions: Apache (2.2.14-5ubuntu8.8), MySQL > (5.1.41-3ubuntu12), Python (2.6.5-0ubuntu1) > > Upgrade history of reviewboard in this server: > 1.6beta1 -> 1.6 -> 1.6.4.1 > > -Antti Paajoki > -- 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
