Re: Help, upgrading to 2.0.7 broke my server!
I ran into the issue as well. Upgraded from 2.0.6 to 2.0.8 with postgres (seems to be the common theme). The steps listed by Christian Wuerdig resolved things. On Thursday, September 25, 2014 4:10:07 PM UTC-4, Christian Wuerdig wrote: I just ran into the same problem upgrading from 2.0.6 to 2.0.8. Running postgres as well In prostgres dropping the index is achieved by: DROP index scmtools_repository_8c446842; running rb-site upgrade again after that completed successfully On Tuesday, 16 September 2014 13:44:48 UTC+12, Christian Hammond wrote: Hmmm, it should have tried to drop the old index in that upgrade. Very odd. What version were you running before this? (I have to take off for a couple hours, but will be back.. hopefully the other instructions will have helped.) Christian -- Christian Hammond - chri...@beanbaginc.com Review Board - https://www.reviewboard.org Beanbag, Inc. - https://www.beanbaginc.com On September 15, 2014 at 6:43:27 PM, Ian (iand...@mac.com) wrote: Upgraded from 2.0.6 and using PostgreSQL. $ sudo rb-site manage /Library/Server/Web/Data/WebApps/ReviewBoard evolve -- --sql Password: -- Evolve application scmtools ALTER TABLE scmtools_repository ADD COLUMN hooks_uuid varchar(32) NULL; CREATE UNIQUE INDEX scmtools_repository_8c446842 ON scmtools_repository (archived_timestamp, path, local_site_id); CREATE UNIQUE INDEX scmtools_repository_f22c3cf5 ON scmtools_repository (hooks_uuid, local_site_id); On Monday, September 15, 2014 6:40:21 PM UTC-7, Christian Hammond wrote: What version did you upgrade from? That looks like it may be a duplicate index. Can you run: rb-site manage /path/to/site evolve -- --sql And show me what that says? Also, are you using MySQL? Christian -- Christian Hammond - chri...@beanbaginc.com Review Board - https://www.reviewboard.org Beanbag, Inc. - https://www.beanbaginc.com On September 15, 2014 at 6:37:05 PM, Ian (iand...@mac.com ) wrote: I did the easy_install -U thing to update Review Board, and then the rb-side upgrade thing to upgrade my site. I get this output though, and now I can't view anything in Review Board. Any workarounds much appreciated! $ sudo rb-site upgrade /Library/Server/Web/Data/WebApps/ReviewBoard Password: Rebuilding directory structure Updating database. This may take a while. The log output below, including warnings and errors, can be ignored unless upgrade fails. -- -- Creating tables ... 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) *CommandError: Error applying evolution: relation scmtools_repository_8c446842 already exists* -- 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 reviewboard...@googlegroups.com . 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 reviewboard...@googlegroups.com. 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 reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: New Review Board 1.7.27 and 2.0.4 security releases
I don't actually see version 2.0.4 at http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ Index of /releases/ReviewBoard/2.0/ -- ReviewBoard-2.0-py2.6.egg http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0-py2.6.eggReviewBoard-2.0-py2.7.egg http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0-py2.7.eggReviewBoard-2.0.1-py2.6.egg http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0.1-py2.6.eggReviewBoard-2.0.1-py2.7.egg http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0.1-py2.7.eggReviewBoard-2.0.1.sha256sum http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0.1.sha256sumReviewBoard-2.0.1.tar.gz http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0.1.tar.gzReviewBoard-2.0.2-py2.6.egg http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0.2-py2.6.eggReviewBoard-2.0.2-py2.7.egg http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0.2-py2.7.eggReviewBoard-2.0.2.sha256sum http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0.2.sha256sumReviewBoard-2.0.2.tar.gz http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0.2.tar.gzReviewBoard-2.0.3-py2.6.egg http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0.3-py2.6.eggReviewBoard-2.0.3-py2.7.egg http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0.3-py2.7.eggReviewBoard-2.0.3.sha256sum http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0.3.sha256sumReviewBoard-2.0.3.tar.gz http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0.3.tar.gzReviewBoard-2.0.sha256sum http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0.sha256sumReviewBoard-2.0.tar.gz http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0.tar.gzReviewBoard-2.0beta1-py2.6.egg http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0beta1-py2.6.eggReviewBoard-2.0beta1-py2.7.egg http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0beta1-py2.7.eggReviewBoard-2.0beta1.sha256sum http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0beta1.sha256sumReviewBoard-2.0beta1.tar.gz http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0beta1.tar.gzReviewBoard-2.0beta2-py2.6.egg http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0beta2-py2.6.eggReviewBoard-2.0beta2-py2.7.egg http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0beta2-py2.7.eggReviewBoard-2.0beta2.sha256sum http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0beta2.sha256sumReviewBoard-2.0beta2.tar.gz http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0beta2.tar.gzReviewBoard-2.0beta3-py2.6.egg http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0beta3-py2.6.eggReviewBoard-2.0beta3-py2.7.egg http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0beta3-py2.7.eggReviewBoard-2.0beta3.sha256sum http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0beta3.sha256sumReviewBoard-2.0beta3.tar.gz http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0beta3.tar.gzReviewBoard-2.0rc1-py2.6.egg http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0rc1-py2.6.eggReviewBoard-2.0rc1-py2.7.egg http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0rc1-py2.7.eggReviewBoard-2.0rc1.sha256sum http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0rc1.sha256sumReviewBoard-2.0rc1.tar.gz http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0rc1.tar.gzReviewBoard-2.0rc2-py2.6.egg http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0rc2-py2.6.eggReviewBoard-2.0rc2-py2.7.egg http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0rc2-py2.7.eggReviewBoard-2.0rc2.sha256sum http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0rc2.sha256sumReviewBoard-2.0rc2.tar.gz http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0rc2.tar.gzReviewBoard-2.0rc3-py2.6.egg http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0rc3-py2.6.eggReviewBoard-2.0rc3-py2.7.egg http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0rc3-py2.7.eggReviewBoard-2.0rc3.sha256sum http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0rc3.sha256sumReviewBoard-2.0rc3.tar.gz http://downloads.reviewboard.org/releases/ReviewBoard/2.0/ReviewBoard-2.0rc3.tar.gz On Tuesday, July 22, 2014 5:23:35 AM UTC-4, Christian Hammond wrote: Hi everyone, We just put out a couple of new Review Board releases: 1.7.27 and 2.0.4. Both fix a couple of security vulnerabilities
Re: Unable to view SVN diff after migration from 1.7.x to 2.0.1
I also get this error when trying to post a new diff for a review that was
created under 1.7.x now that we have upgraded to 2.0.1. We are using
Perforce as the repository (no encodings specified) and using rbt 0.6 to
post the diff. I think the trick is that I'm deleting the binary file
because a quick glance at the code seems to show that both rbt and
ReviewBoard Server have special handling for binary files but for whatever,
reason, the convert_to_unicode function is getting called and obviously
failing. The new post is rejected, but if I view the original post that was
done under 1.7, I get the stacktrace listed in this thread. The rbt output
is as follows:
[...]
Processing delete of //depot/trunk/all/cc/diags/plug_in_charger.rgb
Writing //depot/trunk/all/cc/diags/plug_in_charger.rgb#5 to
/var/folders/my/w5mdtw8j6m588rl_14wpd8frlvhpjq/T/tmpbtm6LW
Running: p4 print -o
/var/folders/my/w5mdtw8j6m588rl_14wpd8frlvhpjq/T/tmpbtm6LW -q
//depot/trunk/all/cc/diags/plug_in_charger.rgb#5
Running: diff -urNp
/var/folders/my/w5mdtw8j6m588rl_14wpd8frlvhpjq/T/tmpbtm6LW
/var/folders/my/w5mdtw8j6m588rl_14wpd8frlvhpjq/T/tmpiX6lxg
Command exited with rc 1: ['diff', '-urNp',
'/var/folders/my/w5mdtw8j6m588rl_14wpd8frlvhpjq/T/tmpbtm6LW',
'/var/folders/my/w5mdtw8j6m588rl_14wpd8frlvhpjq/T/tmpiX6lxg']
--- /var/folders/my/w5mdtw8j6m588rl_14wpd8frlvhpjq/T/tmpbtm6LW 2014-06-04
14:38:08.0 -0400
+++ /var/folders/my/w5mdtw8j6m588rl_14wpd8frlvhpjq/T/tmpiX6lxg 2014-06-04
14:38:08.0 -0400
@@ -1,72 +0,0 @@
-???
[...]
Making HTTP GET request to
http://reviewboard.sonos.com/reviews/api/review-requests/
Making HTTP POST request to
http://reviewboard.sonos.com/reviews/api/review-requests/
Making HTTP GET request to
http://reviewboard.sonos.com/reviews/api/review-requests/7953/diffs/
Making HTTP POST request to
http://reviewboard.sonos.com/reviews/api/review-requests/7953/diffs/
Got API Error 105 (HTTP code 400): One or more fields had errors
Error data: {u'fields': {u'path': [u'unknown encoding: ']}, u'stat':
u'fail', u'err': {u'msg': u'One or more fields had errors', u'code': 105}}
Traceback (most recent call last):
File /usr/local/bin/rbt, line 9, in module
load_entry_point('RBTools==0.6', 'console_scripts', 'rbt')()
File
/Library/Python/2.7/site-packages/RBTools-0.6-py2.7.egg/rbtools/commands/main.py,
line 134, in main
command.run_from_argv([RB_MAIN, command_name] + args)
File
/Library/Python/2.7/site-packages/RBTools-0.6-py2.7.egg/rbtools/commands/__init__.py,
line 422, in run_from_argv
exit_code = self.main(*args) or 0
File
/Library/Python/2.7/site-packages/RBTools-0.6-py2.7.egg/rbtools/commands/post.py,
line 769, in main
submit_as=self.options.submit_as)
File
/Library/Python/2.7/site-packages/RBTools-0.6-py2.7.egg/rbtools/commands/post.py,
line 545, in post_request
raise CommandError('\n'.join(error_msg))
rbtools.commands.CommandError: Error uploading diff
One or more fields had errors (HTTP 400, API Error 105)
path: unknown encoding:
Your review request still exists, but the diff is not attached.
On Monday, June 2, 2014 10:53:46 AM UTC-4, Roudaille77 wrote:
Hello,
I have just updated my ReviewBoard site but I can't visualize the
Subversion diff anymore...
I can see :
There was an error displaying this diff.
Traceback (most recent call last):
File
/usr/local/lib/python2.7/dist-packages/ReviewBoard-2.0.1-py2.7.egg/reviewboard/diffviewer/views.py,
line 236, in get
renderer = self.create_renderer(context, *args, **kwargs)
File
/usr/local/lib/python2.7/dist-packages/ReviewBoard-2.0.1-py2.7.egg/reviewboard/reviews/views.py,
line 1102, in create_renderer
*args, **kwargs)
File
/usr/local/lib/python2.7/dist-packages/ReviewBoard-2.0.1-py2.7.egg/reviewboard/diffviewer/views.py,
line 326, in create_renderer
self.diff_file = self._get_requested_diff_file()
File
/usr/local/lib/python2.7/dist-packages/ReviewBoard-2.0.1-py2.7.egg/reviewboard/diffviewer/views.py,
line 367, in _get_requested_diff_file
request=self.request)
File
/usr/local/lib/python2.7/dist-packages/ReviewBoard-2.0.1-py2.7.egg/reviewboard/diffviewer/diffutils.py,
line 373, in populate_diff_chunks
chunks = generator.get_chunks()
File
/usr/local/lib/python2.7/dist-packages/ReviewBoard-2.0.1-py2.7.egg/reviewboard/diffviewer/chunk_generator.py,
line 148, in get_chunks
large_data=True)
File
/usr/local/lib/python2.7/dist-packages/Djblets-0.8.1-py2.7.egg/djblets/cache/backend.py,
line 109, in cache_memoize
data = lookup_callable()
File
/usr/local/lib/python2.7/dist-packages/ReviewBoard-2.0.1-py2.7.egg/reviewboard/diffviewer/chunk_generator.py,
line 147, in lambda
lambda: list(self._get_chunks_uncached()),
File
/usr/local/lib/python2.7/dist-packages/ReviewBoard-2.0.1-py2.7.egg/reviewboard/diffviewer/chunk_generator.py,
line
Re: rb-site upgrade fails on database migration
I'm getting the exact same error. I'm trying to test an upgrade before
actually performing one on the live server and am getting the same Django
stack trace.
We are running RB 1.5.2 in production on Ubuntu 12.04. I've been using
easy_install to install ReviewBoard and made sure to force the Django
dependency(1.3.3) since the 1.5.2 package pulls in too new of a version. I
used mysqldump to dump the db from the live server and installed a site by
running rb-site install ... and then seeding the database with the
production data through mysql reviewboard dump.sql. I then use
easy_install to upgrade to 1.7.1, which completes but the rb-site upgrade
command fails. However, one thing that I did notice is that I have no issue
upgrading an empty install by doing the same steps as before, but not
seeding the backup database and only upgrading an empty site.
On Tuesday, January 8, 2013 4:34:42 PM UTC-5, virtualAdmin wrote:
We've been making regular backups of our RB 1.5.5 database, and I decided
it was time to verify that we can restore the DB to a new install in case
our server fails. The backups are made with mysqlhotcopy, so I understand
they can be restored by simply stopping the mysql service, copying the
backup files into the appropriate folder (/var/lib/mysql/reviewboard), and
starting mysql.
I installed RB 1.7 on an Ubuntu 12.04 LTS VM. I got the software all
installed and removed the fresh 1.7 database, replacing it with our
backed-up 1.5.5 DB, making sure to set proper privileges on the db files
and in mysql itself.
I ran:
rb-site upgrade -d /var/www/mysite
Which failed, giving this output:
-- begin log output --
Creating tables ...
Creating table attachments_fileattachment
Creating table diffviewer_filediffdata
Creating table hostingsvcs_hostingserviceaccount
Creating table reviews_fileattachmentcomment
Creating table site_localsite_users
Traceback (most recent call last):
File /usr/local/bin/rb-site, line 9, in module
load_entry_point('ReviewBoard==1.7.1', 'console_scripts', 'rb-site')()
File
/usr/local/lib/python2.7/dist-packages/ReviewBoard-1.7.1-py2.7.egg/reviewboard/cmdline/rbsite.py,
line 1937, in main
command.run()
File
/usr/local/lib/python2.7/dist-packages/ReviewBoard-1.7.1-py2.7.egg/reviewboard/cmdline/rbsite.py,
line 1778, in run
site.sync_database()
File
/usr/local/lib/python2.7/dist-packages/ReviewBoard-1.7.1-py2.7.egg/reviewboard/cmdline/rbsite.py,
line 366, in sync_database
self.run_manage_command(syncdb, params)
File
/usr/local/lib/python2.7/dist-packages/ReviewBoard-1.7.1-py2.7.egg/reviewboard/cmdline/rbsite.py,
line 556, in run_manage_command
execute_manager(reviewboard.settings, [__file__, cmd] + params)
File
/usr/local/lib/python2.7/dist-packages/Django-1.4.3-py2.7.egg/django/core/management/__init__.py,
line 459, in execute_manager
utility.execute()
File
/usr/local/lib/python2.7/dist-packages/Django-1.4.3-py2.7.egg/django/core/management/__init__.py,
line 382, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File
/usr/local/lib/python2.7/dist-packages/Django-1.4.3-py2.7.egg/django/core/management/base.py,
line 196, in run_from_argv
self.execute(*args, **options.__dict__)
File
/usr/local/lib/python2.7/dist-packages/Django-1.4.3-py2.7.egg/django/core/management/base.py,
line 232, in execute
output = self.handle(*args, **options)
File
/usr/local/lib/python2.7/dist-packages/Django-1.4.3-py2.7.egg/django/core/management/base.py,
line 371, in handle
return self.handle_noargs(**options)
File
/usr/local/lib/python2.7/dist-packages/Django-1.4.3-py2.7.egg/django/core/management/commands/syncdb.py,
line 102, in handle_noargs
cursor.execute(statement)
File
/usr/local/lib/python2.7/dist-packages/Django-1.4.3-py2.7.egg/django/db/backends/mysql/base.py,
line 114, in execute
return self.cursor.execute(query, args)
File /usr/lib/python2.7/dist-packages/MySQLdb/cursors.py, line 174, in
execute
self.errorhandler(self, exc, value)
File /usr/lib/python2.7/dist-packages/MySQLdb/connections.py, line 36,
in defaulterrorhandler
raise errorclass, errorvalue
django.db.utils.DatabaseError: (1005, Can't create table
'reviewboard.#sql-5a2b_5b' (errno: 150))
Any ideas?
--
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
---
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
Re: rb-site upgrade fails on database migration
Thanks, that solved the issue. Looks like mysql 5.5 defaults to InnoDB but
our original tables were in the older format. I altered them to InnoDB and
everything works now. Thanks,
--Erik
On Tuesday, June 25, 2013 4:26:12 PM UTC-4, Christian Hammond wrote:
That error has to do with having a mix of InnoDB and MyISAM tables. You
need to make sure all tables are the same format. If MySQL is creating new
tables with one, then you should convert the rest.
Christian
--
Christian Hammond - chi...@chipx86.com javascript:
Review Board - http://www.reviewboard.org
Beanbag, Inc. - http://www.beanbaginc.com
On Tue, Jun 25, 2013 at 12:44 PM, Erik Lattimore
erik...@gmail.comjavascript:
wrote:
I'm getting the exact same error. I'm trying to test an upgrade before
actually performing one on the live server and am getting the same Django
stack trace.
We are running RB 1.5.2 in production on Ubuntu 12.04. I've been using
easy_install to install ReviewBoard and made sure to force the Django
dependency(1.3.3) since the 1.5.2 package pulls in too new of a version. I
used mysqldump to dump the db from the live server and installed a site by
running rb-site install ... and then seeding the database with the
production data through mysql reviewboard dump.sql. I then use
easy_install to upgrade to 1.7.1, which completes but the rb-site upgrade
command fails. However, one thing that I did notice is that I have no issue
upgrading an empty install by doing the same steps as before, but not
seeding the backup database and only upgrading an empty site.
On Tuesday, January 8, 2013 4:34:42 PM UTC-5, virtualAdmin wrote:
We've been making regular backups of our RB 1.5.5 database, and I
decided it was time to verify that we can restore the DB to a new install
in case our server fails. The backups are made with mysqlhotcopy, so I
understand they can be restored by simply stopping the mysql service,
copying the backup files into the appropriate folder
(/var/lib/mysql/reviewboard), and starting mysql.
I installed RB 1.7 on an Ubuntu 12.04 LTS VM. I got the software all
installed and removed the fresh 1.7 database, replacing it with our
backed-up 1.5.5 DB, making sure to set proper privileges on the db files
and in mysql itself.
I ran:
rb-site upgrade -d /var/www/mysite
Which failed, giving this output:
-- begin log output --
Creating tables ...
Creating table attachments_fileattachment
Creating table diffviewer_filediffdata
Creating table hostingsvcs_**hostingserviceaccount
Creating table reviews_fileattachmentcomment
Creating table site_localsite_users
Traceback (most recent call last):
File /usr/local/bin/rb-site, line 9, in module
load_entry_point('ReviewBoard=**=1.7.1', 'console_scripts',
'rb-site')()
File /usr/local/lib/python2.7/**dist-packages/ReviewBoard-1.7.**
1-py2.7.egg/reviewboard/**cmdline/rbsite.py, line 1937, in main
command.run()
File /usr/local/lib/python2.7/**dist-packages/ReviewBoard-1.7.**
1-py2.7.egg/reviewboard/**cmdline/rbsite.py, line 1778, in run
site.sync_database()
File /usr/local/lib/python2.7/**dist-packages/ReviewBoard-1.7.**
1-py2.7.egg/reviewboard/**cmdline/rbsite.py, line 366, in sync_database
self.run_manage_command(**syncdb, params)
File /usr/local/lib/python2.7/**dist-packages/ReviewBoard-1.7.**
1-py2.7.egg/reviewboard/**cmdline/rbsite.py, line 556, in
run_manage_command
execute_manager(reviewboard.**settings, [__file__, cmd] + params)
File /usr/local/lib/python2.7/**dist-packages/Django-1.4.3-**
py2.7.egg/django/core/**management/__init__.py, line 459, in
execute_manager
utility.execute()
File /usr/local/lib/python2.7/**dist-packages/Django-1.4.3-**
py2.7.egg/django/core/**management/__init__.py, line 382, in execute
self.fetch_command(subcommand)**.run_from_argv(self.argv)
File /usr/local/lib/python2.7/**dist-packages/Django-1.4.3-**
py2.7.egg/django/core/**management/base.py, line 196, in run_from_argv
self.execute(*args, **options.__dict__)
File /usr/local/lib/python2.7/**dist-packages/Django-1.4.3-**
py2.7.egg/django/core/**management/base.py, line 232, in execute
output = self.handle(*args, **options)
File /usr/local/lib/python2.7/**dist-packages/Django-1.4.3-**
py2.7.egg/django/core/**management/base.py, line 371, in handle
return self.handle_noargs(**options)
File /usr/local/lib/python2.7/**dist-packages/Django-1.4.3-**
py2.7.egg/django/core/**management/commands/syncdb.py**, line 102, in
handle_noargs
cursor.execute(statement)
File /usr/local/lib/python2.7/**dist-packages/Django-1.4.3-**
py2.7.egg/django/db/backends/**mysql/base.py, line 114, in execute
return self.cursor.execute(query, args)
File /usr/lib/python2.7/dist-**packages/MySQLdb/cursors.py, line
174, in execute
self.errorhandler(self, exc, value)
File /usr/lib/python2.7/dist-**packages
