Re: Issue 3394 in reviewboard: Problem with upgrade from 1.7.22 to 2.0.1. Django evolution fails
Updates: Status: NeedInfo Comment #1 on issue 3394 by chip...@gmail.com: Problem with upgrade from 1.7.22 to 2.0.1. Django evolution fails http://code.google.com/p/reviewboard/issues/detail?id=3394 This is almost always due to upgrading, then downgrading, then upgrading again. Or, a previously failed upgrade attempt due to some other error (often a MyISAM vs. InnoDB table difference). Can you show me the output of: rb-site manage /path/to/site list-evolutions Also, was this the very first upgrade attempt? -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- You received this message because you are subscribed to the Google Groups reviewboard-issues group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard-issues+unsubscr...@googlegroups.com. To post to this group, send email to reviewboard-issues@googlegroups.com. Visit this group at http://groups.google.com/group/reviewboard-issues. For more options, visit https://groups.google.com/d/optout.
Re: Issue 3394 in reviewboard: Problem with upgrade from 1.7.22 to 2.0.1. Django evolution fails
Comment #2 on issue 3394 by rafal.wo...@gmail.com: Problem with upgrade from 1.7.22 to 2.0.1. Django evolution fails http://code.google.com/p/reviewboard/issues/detail?id=3394 It is the very first attempt to upgrade this 1.7.22 version to 2.0.1. I am trying to test new 2.0.1 in testing environment separated from my 1.7.22 production instance. I can migrate the database from production with mysqldump or restore the whole environment from backup but the error stops me every time and I do not know what could be wrong. This production instance was upgraded many times but never downgraded. Applied evolutions for 'auth': auth_delete_message auth_unique_together_baseline Applied evolutions for 'contenttypes': contenttypes_unique_together_baseline Applied evolutions for 'sessions': session_expire_date_db_index Applied evolutions for 'accounts': is_private timezone open_an_issue extra_data timezone_length_30 localsiteprofile_permissions unique_together_baseline profile_show_closed Applied evolutions for 'attachments': 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 Applied evolutions for 'changedescs': fields_changed_longtext rich_text Applied evolutions for 'diffviewer': add_parent_diffs filediff_filenames_1024_chars diffset_basedir filediff_status add_diff_hash diffsethistory_diff_updated diffset_base_commit_id filediffdata_line_counts filediffdata_extra_data all_extra_data Applied evolutions for 'hostingsvcs': account_hosting_url account_hosting_url_max_length_255 account_unique_together_baseline Applied evolutions for 'reviews': change_descriptions last_review_timestamp shipit_count default_reviewer_repositories null_repository localsite group_incoming_request_count group_invite_only group_visible default_reviewer_local_site add_issues_to_comments file_attachments file_attachment_comment_extra_data review_request_last_review_activity_timestamp review_request_depends_on commit_id file_attachment_comment_diff_id rich_text base_comment_extra_data unique_together_baseline extra_data review_request_issue_counts group_mailing_list_charfield review_request_draft_commit_id Applied evolutions for 'scmtools': bugzilla_url_charfield repository_raw_file_url repository_visible repository_path_length_255 localsite repository_access_control group_site repository_hosting_accounts repository_extra_data_null unique_together_baseline Applied evolutions for 'site': localsite_public -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- You received this message because you are subscribed to the Google Groups reviewboard-issues group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard-issues+unsubscr...@googlegroups.com. To post to this group, send email to reviewboard-issues@googlegroups.com. Visit this group at http://groups.google.com/group/reviewboard-issues. For more options, visit https://groups.google.com/d/optout.
Re: Issue 3394 in reviewboard: Problem with upgrade from 1.7.22 to 2.0.1. Django evolution fails
Comment #3 on issue 3394 by rafal.wo...@gmail.com: Problem with upgrade from 1.7.22 to 2.0.1. Django evolution fails http://code.google.com/p/reviewboard/issues/detail?id=3394 After few more tries I managed to finish rb-site upgrade without any errors :) Unfortunately I cannot tell what I did wrong and what solved the problem, sorry. At the moment I have another problem with formatting in review request window (please see attached image). Text areas seem to be badly formatted and too wide. It occurs only for migrated review requests. Newly created review requests look well, as it should. I confirmed the formatting problem in chromium-browser, firefox and IE8. Could it be upgrading/evolution related issue? Attachments: review_problem.png 21.9 KB -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- You received this message because you are subscribed to the Google Groups reviewboard-issues group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard-issues+unsubscr...@googlegroups.com. To post to this group, send email to reviewboard-issues@googlegroups.com. Visit this group at http://groups.google.com/group/reviewboard-issues. For more options, visit https://groups.google.com/d/optout.
Re: Issue 3394 in reviewboard: Problem with upgrade from 1.7.22 to 2.0.1. Django evolution fails
Updates: Status: SetupIssue Comment #4 on issue 3394 by chip...@gmail.com: Problem with upgrade from 1.7.22 to 2.0.1. Django evolution fails http://code.google.com/p/reviewboard/issues/detail?id=3394 Can you please file a separate bug for the text areas? We keep bug reports to one incident per report. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- You received this message because you are subscribed to the Google Groups reviewboard-issues group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard-issues+unsubscr...@googlegroups.com. To post to this group, send email to reviewboard-issues@googlegroups.com. Visit this group at http://groups.google.com/group/reviewboard-issues. For more options, visit https://groups.google.com/d/optout.
