Thanks for thinking about this. The problem was that I was updating
from a neolithic Reviewboard (pre 1.0, commit # 1151).
After untangling all of the errors, I realized I was missing an
encoding column, and added it manually. Then forced the DB update to
go through for version 1.5.5 (since that was a smaller change). Once
I had that, I could run site-upgrade successfully. Then I cleanly
went to 1.6.2 and all was good.
Many thanks!
-ben
On Wed, Nov 09, 2011 at 11:19:02AM -0800, Christian Hammond wrote:
> Wow, it sure is.
>
> What version did you try upgrading from?
>
> What type of database are you using?
>
> Issues like this generally only crop up when someone has made modifications
> to Review Board or in some way hand-altered the database. Is your copy
> vanilla upstream, or was anything custom ever done on any level?
>
> Christian
>
>
> On Wednesday, November 9, 2011, Ben Bennett <knob...@gmail.com> wrote:
> > 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
>
> --
> --
> Christian Hammond - chip...@chipx86.com
> Review Board - http://www.reviewboard.org
> VMware, Inc. - http://www.vmware.com
>
> --
> 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
