Re: Upgrading Review Board from 1.0.5.1 to 2.0.15
Thanks Christian
Is enough to run?
easy_install -U django_evolution
Best
El lunes, 13 de abril de 2015, 21:13:50 (UTC-6), Christian Hammond escribió:
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@gmail.com
javascript: 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
Re: Upgrading Review Board from 1.0.5.1 to 2.0.15
Thank you Christian,
I confirm It works!
El lunes, 13 de abril de 2015, 21:13:50 (UTC-6), Christian Hammond escribió:
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@gmail.com
javascript: 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
Re: Upgrading Review Board from 1.0.5.1 to 2.0.15
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
