Hi Rodrigo,

This is due to a bug in the current version of Django Evolution. We have
fixes pending for a release. I'll work to get that out tonight. Tomorrow,
upgrade the django_evolution package, and you should be good.

Christian


On Monday, April 13, 2015, Rodrigo Castro <rodrigo.b.cas...@gmail.com>
wrote:

>
> Hello,
>
> I am trying to upgrade rb from 1.0.5 to 2.0.15 (in the attachment the old
> db schema)
>
> I am following this steps.
>
> 1. Install a fresh new 2.0.15
> 2. Restore the old 1.0.5 database (in replace of the newer one that I just
> installed)
> 3. Execute rb-site upgrade /var/www/rb.searchrev.com/
>
> But I am getting the following errors.
>
>
> [root@reviewboard conf]# rb-site upgrade /var/www/rb.searchrev.com/
> 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 ...
> Creating table extensions_registeredextension
> Creating table accounts_localsiteprofile
> Creating table attachments_fileattachment
> Creating table diffviewer_filediffdata
> Creating table hostingsvcs_hostingserviceaccount
> Creating table reviews_fileattachmentcomment
> Creating table site_localsite_users
> Creating table site_localsite_admins
> Creating table site_localsite
> Upgrading Review Board from 1.0.5.1 to 2.0.15
> There are unapplied evolutions for auth.
> There are unapplied evolutions for contenttypes.
> There are unapplied evolutions for sessions.
> 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.
> Adding baseline version for new models
> Evolutions in attachments baseline: file_attachment_orig_filename,
> file_attachment_file_max_length_512, file_attachment_repo_info,
> file_attachment_repo_path_no_index,
> file_attachment_repo_revision_max_length_64
> Evolutions in site baseline: localsite_public
> Evolutions in hostingsvcs baseline: account_hosting_url,
> account_hosting_url_max_length_255, account_unique_together_baseline
> Project signature has changed - an evolution is required
> Installing custom SQL ...
> Installing indexes ...
> Installed 0 object(s) from 0 fixture(s)
> Registering new SCM Tool Plastic SCM
> (reviewboard.scmtools.plastic.PlasticTool) in database
> 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:
> The application markup has been deleted
> In model reviews.DefaultReviewer:
>     In field 'repository':
>         Property 'null' has changed
> In model reviews.ReviewRequest:
>     In field 'repository':
>         Property 'null' has changed
> CommandError: Your models contain changes that Django Evolution cannot
> resolve automatically.
>
>
>
> In a second attempt I read I need to copy some data from the newer
> database in order to complete the upgrade.
>
> in the old database
>
> insert into django_evolution select * from rb_install.django_evolution;
> insert into django_project_version select * from
> rb_install.django_project_version;
>
> and then try again the upgrade
>
> But after that I am getting this error.
>
> [root@reviewboard conf]# rb-site upgrade /var/www/rb.searchrev.com/
> 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 ...
> Creating table extensions_registeredextension
> Creating table accounts_localsiteprofile
> Creating table attachments_fileattachment
> Creating table diffviewer_filediffdata
> Creating table hostingsvcs_hostingserviceaccount
> Creating table reviews_fileattachmentcomment
> Creating table site_localsite_users
> Creating table site_localsite_admins
> Creating table site_localsite
> Upgrading Review Board from 1.0.5.1 to 2.0.15
> Installing custom SQL ...
> Installing indexes ...
> Installed 0 object(s) from 0 fixture(s)
> Registering new SCM Tool Plastic SCM
> (reviewboard.scmtools.plastic.PlasticTool) in database
> No evolution required.
> ------------------- <end log output> -------------------
>
> Resetting in-database caches.
> Traceback (most recent call last):
>   File "/usr/bin/rb-site", line 9, in <module>
>     load_entry_point('ReviewBoard==2.0.15', 'console_scripts', 'rb-site')()
>   File "/usr/lib/python2.7/site-packages/reviewboard/cmdline/rbsite.py",
> line 1885, in main
>     command.run()
>   File "/usr/lib/python2.7/site-packages/reviewboard/cmdline/rbsite.py",
> line 1698, in run
>     site.run_manage_command("fixreviewcounts")
>   File "/usr/lib/python2.7/site-packages/reviewboard/cmdline/rbsite.py",
> line 662, in run_manage_command
>     execute_from_command_line([__file__, cmd] + params)
>   File
> "/usr/lib/python2.7/site-packages/django/core/management/__init__.py", line
> 399, in execute_from_command_line
>     utility.execute()
>   File
> "/usr/lib/python2.7/site-packages/django/core/management/__init__.py", line
> 392, in execute
>     self.fetch_command(subcommand).run_from_argv(self.argv)
>   File "/usr/lib/python2.7/site-packages/django/core/management/base.py",
> line 242, in run_from_argv
>     self.execute(*args, **options.__dict__)
>   File "/usr/lib/python2.7/site-packages/django/core/management/base.py",
> line 285, in execute
>     output = self.handle(*args, **options)
>   File "/usr/lib/python2.7/site-packages/django/core/management/base.py",
> line 415, in handle
>     return self.handle_noargs(**options)
>   File
> "/usr/lib/python2.7/site-packages/reviewboard/reviews/management/commands/fixreviewcounts.py",
> line 12, in handle_noargs
>     fix_review_counts()
>   File "/usr/lib/python2.7/site-packages/reviewboard/accounts/admin.py",
> line 137, in fix_review_counts
>     Group.objects.update(incoming_request_count=None)
>   File "/usr/lib/python2.7/site-packages/django/db/models/manager.py",
> line 214, in update
>     return self.get_queryset().update(*args, **kwargs)
>   File "/usr/lib/python2.7/site-packages/django/db/models/query.py", line
> 493, in update
>     rows = query.get_compiler(self.db).execute_sql(None)
>   File
> "/usr/lib/python2.7/site-packages/django/db/models/sql/compiler.py", line
> 980, in execute_sql
>     cursor = super(SQLUpdateCompiler, self).execute_sql(result_type)
>   File
> "/usr/lib/python2.7/site-packages/django/db/models/sql/compiler.py", line
> 786, in execute_sql
>     cursor.execute(sql, params)
>   File "/usr/lib/python2.7/site-packages/django/db/backends/util.py", line
> 53, in execute
>     return self.cursor.execute(sql, params)
>   File "/usr/lib/python2.7/site-packages/django/db/utils.py", line 99, in
> __exit__
>     six.reraise(dj_exc_type, dj_exc_value, traceback)
>   File "/usr/lib/python2.7/site-packages/django/db/backends/util.py", line
> 53, in execute
>     return self.cursor.execute(sql, params)
>   File
> "/usr/lib/python2.7/site-packages/django/db/backends/mysql/base.py", line
> 124, in execute
>     return self.cursor.execute(query, args)
>   File "/usr/lib64/python2.7/site-packages/MySQLdb/cursors.py", line 174,
> in execute
>     self.errorhandler(self, exc, value)
>   File "/usr/lib64/python2.7/site-packages/MySQLdb/connections.py", line
> 36, in defaulterrorhandler
>     raise errorclass, errorvalue
> django.db.utils.OperationalError: (1054, "Unknown column
> 'incoming_request_count' in 'field list'")
>
>
> If you can help I really appreciate .
>
>
> BR
>
> --
> Supercharge your Review Board with Power Pack:
> https://www.reviewboard.org/powerpack/
> Want us to host Review Board for you? Check out RBCommons:
> https://rbcommons.com/
> Happy user? Let us know! https://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
> <javascript:_e(%7B%7D,'cvml','reviewboard%2bunsubscr...@googlegroups.com');>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
-- 
Christian Hammond - christ...@beanbaginc.com
Review Board - http://www.reviewboard.org
Beanbag, Inc. - http://www.beanbaginc.com

-- 
Supercharge your Review Board with Power Pack: 
https://www.reviewboard.org/powerpack/
Want us to host Review Board for you? Check out RBCommons: 
https://rbcommons.com/
Happy user? Let us know! https://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.

Reply via email to