Problem upgrading from 1.6.9 to 2.0.1
I'm attempting a Reviewboard 1.6.9-2.0 migration. This is on Ubuntu 12.04 and I'm using postgresql as the database. I've updated review-board with this command: sudo easy_install -U ReviewBoard Based on the release notes, I went ahead and removed PIL and installed pillow, but then rb-site did not even run. I re-installed PIL with sudo easy_install pil and then I get this error when I run sudo rb-site upgrade /var/www/review-board: Traceback (most recent call last): File /usr/local/bin/rb-site, line 9, in module load_entry_point('ReviewBoard==2.0.1', 'console_scripts', 'rb-site')() File /usr/local/lib/python2.7/dist-packages/ReviewBoard-2.0.1-py2.7.egg/reviewboard/cmdline/rbsite.py, line 1733, in main command.run() File /usr/local/lib/python2.7/dist-packages/ReviewBoard-2.0.1-py2.7.egg/reviewboard/cmdline/rbsite.py, line 1536, in run diff_dedup_needed = site.get_diff_dedup_needed() File /usr/local/lib/python2.7/dist-packages/ReviewBoard-2.0.1-py2.7.egg/reviewboard/cmdline/rbsite.py, line 442, in get_diff_dedup_needed return FileDiff.objects.unmigrated().count() 0 File /usr/local/lib/python2.7/dist-packages/Django-1.6.5-py2.7.egg/django/db/models/query.py, line 294, in count return self.query.get_count(using=self.db) File /usr/local/lib/python2.7/dist-packages/Django-1.6.5-py2.7.egg/django/db/models/sql/query.py, line 390, in get_count number = obj.get_aggregation(using=using)[None] File /usr/local/lib/python2.7/dist-packages/Django-1.6.5-py2.7.egg/django/db/models/sql/query.py, line 356, in get_aggregation result = query.get_compiler(using).execute_sql(SINGLE) File /usr/local/lib/python2.7/dist-packages/Django-1.6.5-py2.7.egg/django/db/models/sql/compiler.py, line 786, in execute_sql cursor.execute(sql, params) File /usr/local/lib/python2.7/dist-packages/Django-1.6.5-py2.7.egg/django/db/backends/util.py, line 69, in execute return super(CursorDebugWrapper, self).execute(sql, params) File /usr/local/lib/python2.7/dist-packages/Django-1.6.5-py2.7.egg/django/db/backends/util.py, line 53, in execute return self.cursor.execute(sql, params) File /usr/local/lib/python2.7/dist-packages/Django-1.6.5-py2.7.egg/django/db/utils.py, line 99, in __exit__ six.reraise(dj_exc_type, dj_exc_value, traceback) File /usr/local/lib/python2.7/dist-packages/Django-1.6.5-py2.7.egg/django/db/backends/util.py, line 53, in execute return self.cursor.execute(sql, params) django.db.utils.ProgrammingError: column diffviewer_filediff.diff_hash_id does not exist LINE 1: ...CT COUNT(*) FROM diffviewer_filediff WHERE NOT (diffviewe... Based on some comments in similar threads, I went into the rbsite.py file and made the site.get_diff_dedup_needed function return True to get past this error, but then I end up with another error: 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. There are unapplied evolutions for site. Project signature has changed - an evolution is required Installing custom SQL ... Installing indexes ... Installed 0 object(s) from 0 fixture(s) ERROR:root:Unexpected error: 'NoneType' object is not iterable Traceback (most recent call last): File /usr/local/lib/python2.7/dist-packages/django_evolution-0.7.1-py2.7.egg/django_evolution/management/commands/evolve.py, line 65, in handle self.evolve(*app_labels, **options) File /usr/local/lib/python2.7/dist-packages/django_evolution-0.7.1-py2.7.egg/django_evolution/management/commands/evolve.py, line 125, in evolve sql.extend(self.evolve_app(app)) File /usr/local/lib/python2.7/dist-packages/django_evolution-0.7.1-py2.7.egg/django_evolution/management/commands/evolve.py, line 165, in evolve_app app_mutator_sql = app_mutator.to_sql() File /usr/local/lib/python2.7/dist-packages/django_evolution-0.7.1-py2.7.egg/django_evolution/mutators.py, line 303, in to_sql sql.extend(mutator.to_sql()) File /usr/local/lib/python2.7/dist-packages/django_evolution-0.7.1-py2.7.egg/django_evolution/mutators.py, line 186, in to_sql return self.evolver.generate_table_ops_sql(self, self._ops) File /usr/local/lib/python2.7/dist-packages/django_evolution-0.7.1-py2.7.egg/django_evolution/db/common.py, line 42, in generate_table_ops_sql
Re: Problem upgrading from 1.6.9 to 2.0.1
Looks like there was a similar bug in the Postgres backend. I'm working on a fix now, and will reply when there's a new Django Evolution version for you to try. Christian -- Christian Hammond - chip...@chipx86.com Review Board - http://www.reviewboard.org Beanbag, Inc. - http://www.beanbaginc.com On Mon, Jun 2, 2014 at 2:23 PM, Thomas Allen tho...@agilelaw.com wrote: I'm attempting a Reviewboard 1.6.9-2.0 migration. This is on Ubuntu 12.04 and I'm using postgresql as the database. I've updated review-board with this command: sudo easy_install -U ReviewBoard Based on the release notes, I went ahead and removed PIL and installed pillow, but then rb-site did not even run. I re-installed PIL with sudo easy_install pil and then I get this error when I run sudo rb-site upgrade /var/www/review-board: Traceback (most recent call last): File /usr/local/bin/rb-site, line 9, in module load_entry_point('ReviewBoard==2.0.1', 'console_scripts', 'rb-site')() File /usr/local/lib/python2.7/dist-packages/ReviewBoard-2.0.1-py2.7.egg/reviewboard/cmdline/rbsite.py, line 1733, in main command.run() File /usr/local/lib/python2.7/dist-packages/ReviewBoard-2.0.1-py2.7.egg/reviewboard/cmdline/rbsite.py, line 1536, in run diff_dedup_needed = site.get_diff_dedup_needed() File /usr/local/lib/python2.7/dist-packages/ReviewBoard-2.0.1-py2.7.egg/reviewboard/cmdline/rbsite.py, line 442, in get_diff_dedup_needed return FileDiff.objects.unmigrated().count() 0 File /usr/local/lib/python2.7/dist-packages/Django-1.6.5-py2.7.egg/django/db/models/query.py, line 294, in count return self.query.get_count(using=self.db) File /usr/local/lib/python2.7/dist-packages/Django-1.6.5-py2.7.egg/django/db/models/sql/query.py, line 390, in get_count number = obj.get_aggregation(using=using)[None] File /usr/local/lib/python2.7/dist-packages/Django-1.6.5-py2.7.egg/django/db/models/sql/query.py, line 356, in get_aggregation result = query.get_compiler(using).execute_sql(SINGLE) File /usr/local/lib/python2.7/dist-packages/Django-1.6.5-py2.7.egg/django/db/models/sql/compiler.py, line 786, in execute_sql cursor.execute(sql, params) File /usr/local/lib/python2.7/dist-packages/Django-1.6.5-py2.7.egg/django/db/backends/util.py, line 69, in execute return super(CursorDebugWrapper, self).execute(sql, params) File /usr/local/lib/python2.7/dist-packages/Django-1.6.5-py2.7.egg/django/db/backends/util.py, line 53, in execute return self.cursor.execute(sql, params) File /usr/local/lib/python2.7/dist-packages/Django-1.6.5-py2.7.egg/django/db/utils.py, line 99, in __exit__ six.reraise(dj_exc_type, dj_exc_value, traceback) File /usr/local/lib/python2.7/dist-packages/Django-1.6.5-py2.7.egg/django/db/backends/util.py, line 53, in execute return self.cursor.execute(sql, params) django.db.utils.ProgrammingError: column diffviewer_filediff.diff_hash_id does not exist LINE 1: ...CT COUNT(*) FROM diffviewer_filediff WHERE NOT (diffviewe... Based on some comments in similar threads, I went into the rbsite.py file and made the site.get_diff_dedup_needed function return True to get past this error, but then I end up with another error: 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. There are unapplied evolutions for site. Project signature has changed - an evolution is required Installing custom SQL ... Installing indexes ... Installed 0 object(s) from 0 fixture(s) ERROR:root:Unexpected error: 'NoneType' object is not iterable Traceback (most recent call last): File /usr/local/lib/python2.7/dist-packages/django_evolution-0.7.1-py2.7.egg/django_evolution/management/commands/evolve.py, line 65, in handle self.evolve(*app_labels, **options) File /usr/local/lib/python2.7/dist-packages/django_evolution-0.7.1-py2.7.egg/django_evolution/management/commands/evolve.py, line 125, in evolve sql.extend(self.evolve_app(app)) File /usr/local/lib/python2.7/dist-packages/django_evolution-0.7.1-py2.7.egg/django_evolution/management/commands/evolve.py, line 165, in evolve_app app_mutator_sql = app_mutator.to_sql() File /usr/local/lib/python2.7/dist-packages/django_evolution-0.7.1-py2.7.egg/django_evolution/mutators.py, line 303, in to_sql sql.extend(mutator.to_sql()) File
Re: Problem upgrading from 1.6.9 to 2.0.1
Go ahead and update django_evolution: $ sudo easy_install -U django_evolution The 0.7.2 release should hopefully fix these issues. Christian -- Christian Hammond - chip...@chipx86.com Review Board - http://www.reviewboard.org Beanbag, Inc. - http://www.beanbaginc.com On Mon, Jun 2, 2014 at 3:08 PM, Christian Hammond chip...@chipx86.com wrote: Looks like there was a similar bug in the Postgres backend. I'm working on a fix now, and will reply when there's a new Django Evolution version for you to try. Christian -- Christian Hammond - chip...@chipx86.com Review Board - http://www.reviewboard.org Beanbag, Inc. - http://www.beanbaginc.com On Mon, Jun 2, 2014 at 2:23 PM, Thomas Allen tho...@agilelaw.com wrote: I'm attempting a Reviewboard 1.6.9-2.0 migration. This is on Ubuntu 12.04 and I'm using postgresql as the database. I've updated review-board with this command: sudo easy_install -U ReviewBoard Based on the release notes, I went ahead and removed PIL and installed pillow, but then rb-site did not even run. I re-installed PIL with sudo easy_install pil and then I get this error when I run sudo rb-site upgrade /var/www/review-board: Traceback (most recent call last): File /usr/local/bin/rb-site, line 9, in module load_entry_point('ReviewBoard==2.0.1', 'console_scripts', 'rb-site')() File /usr/local/lib/python2.7/dist-packages/ReviewBoard-2.0.1-py2.7.egg/reviewboard/cmdline/rbsite.py, line 1733, in main command.run() File /usr/local/lib/python2.7/dist-packages/ReviewBoard-2.0.1-py2.7.egg/reviewboard/cmdline/rbsite.py, line 1536, in run diff_dedup_needed = site.get_diff_dedup_needed() File /usr/local/lib/python2.7/dist-packages/ReviewBoard-2.0.1-py2.7.egg/reviewboard/cmdline/rbsite.py, line 442, in get_diff_dedup_needed return FileDiff.objects.unmigrated().count() 0 File /usr/local/lib/python2.7/dist-packages/Django-1.6.5-py2.7.egg/django/db/models/query.py, line 294, in count return self.query.get_count(using=self.db) File /usr/local/lib/python2.7/dist-packages/Django-1.6.5-py2.7.egg/django/db/models/sql/query.py, line 390, in get_count number = obj.get_aggregation(using=using)[None] File /usr/local/lib/python2.7/dist-packages/Django-1.6.5-py2.7.egg/django/db/models/sql/query.py, line 356, in get_aggregation result = query.get_compiler(using).execute_sql(SINGLE) File /usr/local/lib/python2.7/dist-packages/Django-1.6.5-py2.7.egg/django/db/models/sql/compiler.py, line 786, in execute_sql cursor.execute(sql, params) File /usr/local/lib/python2.7/dist-packages/Django-1.6.5-py2.7.egg/django/db/backends/util.py, line 69, in execute return super(CursorDebugWrapper, self).execute(sql, params) File /usr/local/lib/python2.7/dist-packages/Django-1.6.5-py2.7.egg/django/db/backends/util.py, line 53, in execute return self.cursor.execute(sql, params) File /usr/local/lib/python2.7/dist-packages/Django-1.6.5-py2.7.egg/django/db/utils.py, line 99, in __exit__ six.reraise(dj_exc_type, dj_exc_value, traceback) File /usr/local/lib/python2.7/dist-packages/Django-1.6.5-py2.7.egg/django/db/backends/util.py, line 53, in execute return self.cursor.execute(sql, params) django.db.utils.ProgrammingError: column diffviewer_filediff.diff_hash_id does not exist LINE 1: ...CT COUNT(*) FROM diffviewer_filediff WHERE NOT (diffviewe... Based on some comments in similar threads, I went into the rbsite.py file and made the site.get_diff_dedup_needed function return True to get past this error, but then I end up with another error: 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. There are unapplied evolutions for site. Project signature has changed - an evolution is required Installing custom SQL ... Installing indexes ... Installed 0 object(s) from 0 fixture(s) ERROR:root:Unexpected error: 'NoneType' object is not iterable Traceback (most recent call last): File /usr/local/lib/python2.7/dist-packages/django_evolution-0.7.1-py2.7.egg/django_evolution/management/commands/evolve.py, line 65, in handle self.evolve(*app_labels, **options) File /usr/local/lib/python2.7/dist-packages/django_evolution-0.7.1-py2.7.egg/django_evolution/management/commands/evolve.py, line 125, in evolve sql.extend(self.evolve_app(app)) File