When tryhing to go to 1.6.1 I get:
# rb-site upgrade /var/www/localhost/reviewboard
Rebuilding directory structure
Updating database. This may take a while.
Creating tables ...
There are unapplied evolutions for accounts.
There are unapplied evolutions for changedescs.
There are unapplied evolutions for reviews.
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.
Traceback (most recent call last):
  File "/usr/bin/rb-site-2.7", line 9, in <module>
    load_entry_point('ReviewBoard==1.6.1', 'console_scripts', 'rb-
site')()
  File "/usr/lib/python2.7/site-packages/reviewboard/cmdline/
rbsite.py", line 1747, in main
    command.run()
  File "/usr/lib/python2.7/site-packages/reviewboard/cmdline/
rbsite.py", line 1645, in run
    site.migrate_database()
  File "/usr/lib/python2.7/site-packages/reviewboard/cmdline/
rbsite.py", line 353, in migrate_database
    self.run_manage_command("evolve", ["--noinput", "--execute"])
  File "/usr/lib/python2.7/site-packages/reviewboard/cmdline/
rbsite.py", line 472, in run_manage_command
    execute_manager(reviewboard.settings, [__file__, cmd] + params)
  File "/usr/lib/python2.7/site-packages/django/core/management/
__init__.py", line 438, in execute_manager
    utility.execute()
  File "/usr/lib/python2.7/site-packages/django/core/management/
__init__.py", line 379, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/usr/lib/python2.7/site-packages/django/core/management/
base.py", line 191, in run_from_argv
    self.execute(*args, **options.__dict__)
  File "/usr/lib/python2.7/site-packages/django/core/management/
base.py", line 220, in execute
    output = self.handle(*args, **options)
  File "/usr/lib/python2.7/site-packages/django_evolution/management/
commands/evolve.py", line 60, in handle
    self.evolve(*app_labels, **options)
  File "/usr/lib/python2.7/site-packages/django_evolution/management/
commands/evolve.py", line 140, in evolve
    database))
  File "/usr/lib/python2.7/site-packages/django_evolution/
mutations.py", line 418, in mutate
    return self.add_column(app_label, proj_sig, database)
  File "/usr/lib/python2.7/site-packages/django_evolution/
mutations.py", line 426, in add_column
    self.field_attrs, model)
  File "/usr/lib/python2.7/site-packages/django_evolution/
mutations.py", line 33, in create_field
    related_model_sig = proj_sig[related_app_name][related_model_name]


I see the same error message in Google with a follow-up indicating
that it was fixed by a syncdb, so I tried that:
# rb-site manage /var/www/localhost/reviewboard syncdb
Creating tables ...
There are unapplied evolutions for accounts.
There are unapplied evolutions for changedescs.
There are unapplied evolutions for reviews.
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.

Then I re-run the upgrade and it gets the same error.  If I manually
run:
# rb-site manage /var/www/localhost/reviewboard evolve -- -x

I get the same error.

Any assistance would be greatly appreciated.


-- 
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

Reply via email to