Re: Upgrading database/site from 1.0 to 1.6.1
It turns out that the reason Review Board thought my database hadn't been updated was because it hadn't: I had moved the site onto my new machine and not updated the relevant paths in /conf/*. My current status is that I now have two perfectly working sites, the legacy running off SQLite and production running off MySQL. It would be nice to be able to merge them up, but when I try and load my dumpfile I get merely No fixtures found. even with -d. Is there any gotchas I might have missed? If not, many thanks to everyone who took the time to help and in particular to Christian for his patience and help with what must seem like incessant requests. Sandeep -- 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
Re: Upgrading database/site from 1.0 to 1.6.1
I'm happy to help, Sandeep :) I'm particularly glad it's working for you now. Merging databases is, well, nearly impossible right now. You'd end up with a broken mess, since entries in tables reference others by ID, and those IDs would change. A custom extraction/merging tool would need to be developed, which would be a great project for someone to do (maybe we will someday, but not any time soon). Christian -- Christian Hammond - chip...@chipx86.com Review Board - http://www.reviewboard.org VMware, Inc. - http://www.vmware.com On Tue, Sep 27, 2011 at 12:31 PM, insysion s.tai...@insysion.net wrote: It turns out that the reason Review Board thought my database hadn't been updated was because it hadn't: I had moved the site onto my new machine and not updated the relevant paths in /conf/*. My current status is that I now have two perfectly working sites, the legacy running off SQLite and production running off MySQL. It would be nice to be able to merge them up, but when I try and load my dumpfile I get merely No fixtures found. even with -d. Is there any gotchas I might have missed? If not, many thanks to everyone who took the time to help and in particular to Christian for his patience and help with what must seem like incessant requests. Sandeep -- 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
Re: Upgrading database/site from 1.0 to 1.6.1
Hi Christian, Please find attached the console output when I try to upgrade my old site. As I said, if I tried to point a fresh 1.6.1 site at the supposedly upgraded database it claims that Manual server updates required Review Board. I think I'm going to trying dumping and loading the JSON data in the new mySQL site but I need to ensure the database has been properly upgraded. How can I ascertain this by directly querying it? Warm regards, Sandeep -- 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=encpli6011:/var/www # rb-site upgrade reviewboard.test.com Rebuilding directory structure Updating database. This may take a while. Creating tables ... Creating table django_admin_log Creating table auth_permission Creating table auth_group_permissions Creating table auth_group Creating table auth_user_user_permissions Creating table auth_user_groups Creating table auth_user Creating table auth_message Creating table django_content_type Creating table django_site Creating table django_session Creating table siteconfig_siteconfiguration Creating table accounts_reviewrequestvisit Creating table accounts_profile_starred_review_requests Creating table accounts_profile_starred_groups Creating table accounts_profile Creating table accounts_localsiteprofile Creating table attachments_fileattachment Creating table changedescs_changedescription Creating table diffviewer_filediff Creating table diffviewer_diffset Creating table diffviewer_diffsethistory Creating table reviews_group_users Creating table reviews_group Creating table reviews_defaultreviewer_repository Creating table reviews_defaultreviewer_people Creating table reviews_defaultreviewer_groups Creating table reviews_defaultreviewer Creating table reviews_screenshot Creating table reviews_reviewrequest_changedescs Creating table reviews_reviewrequest_target_people Creating table reviews_reviewrequest_inactive_screenshots Creating table reviews_reviewrequest_screenshots Creating table reviews_reviewrequest_inactive_file_attachments Creating table reviews_reviewrequest_target_groups Creating table reviews_reviewrequest_file_attachments Creating table reviews_reviewrequest Creating table reviews_reviewrequestdraft_target_people Creating table reviews_reviewrequestdraft_inactive_screenshots Creating table reviews_reviewrequestdraft_file_attachments Creating table reviews_reviewrequestdraft_screenshots Creating table reviews_reviewrequestdraft_inactive_file_attachments Creating table reviews_reviewrequestdraft_target_groups Creating table reviews_reviewrequestdraft Creating table reviews_comment Creating table reviews_screenshotcomment Creating table reviews_fileattachmentcomment Creating table reviews_review_comments Creating table reviews_review_file_attachment_comments Creating table reviews_review_screenshot_comments Creating table reviews_review Creating table scmtools_tool Creating table scmtools_repository_review_groups Creating table scmtools_repository_users Creating table scmtools_repository Creating table site_localsite_users Creating table site_localsite_admins Creating table site_localsite Creating table django_project_version Creating table django_evolution Registering new SCM Tool Subversion (reviewboard.scmtools.svn.SVNTool) in database Registering new SCM Tool Git (reviewboard.scmtools.git.GitTool) in database Registering new SCM Tool Bazaar (reviewboard.scmtools.bzr.BZRTool) in database Registering new SCM Tool CVS (reviewboard.scmtools.cvs.CVSTool) in database Registering new SCM Tool Perforce (reviewboard.scmtools.perforce.PerforceTool) in database Registering new SCM Tool Plastic SCM (reviewboard.scmtools.plastic.PlasticTool) in database Registering new SCM Tool ClearCase (reviewboard.scmtools.clearcase.ClearCaseTool) in database Registering new SCM Tool Mercurial (reviewboard.scmtools.hg.HgTool) in database Installing baseline version Evolutions in sessions baseline: session_expire_date_db_index Evolutions in accounts baseline: is_private Evolutions in diffviewer baseline: add_parent_diffs, filediff_filenames_1024_chars, diffset_basedir, filediff_status Evolutions in reviews baseline: 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 Evolutions in scmtools baseline: bugzilla_url_charfield, repository_raw_file_url, repository_visible, repository_path_length_255, localsite, repository_access_control, group_site Installing custom SQL ... Installing indexes ... No fixtures found. No evolution required.
Re: Upgrading database/site from 1.0 to 1.6.1
Hi, There are many different Manual Update pages. I need to know exactly what you're seeing. Can you attach it as an HTML page? Christian On Monday, September 26, 2011, insysion s.tai...@insysion.net wrote: Hi Christian, Please find attached the console output when I try to upgrade my old site. As I said, if I tried to point a fresh 1.6.1 site at the supposedly upgraded database it claims that Manual server updates required Review Board. I think I'm going to trying dumping and loading the JSON data in the new mySQL site but I need to ensure the database has been properly upgraded. How can I ascertain this by directly querying it? Warm regards, Sandeep -- 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 reviewboard%2bunsubscr...@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
changing backends Re: Upgrading database/site from 1.0 to 1.6.1
Christian Hammond wrote: [RE changing backend databases] Unofficially, you can do the following: On the old site: rb-site manage /path/to/site dumpdata dbdump.json On the new: . loaddata dbdump.json There are no guarantees it'll work, but give it a try. Note: They will both need to be updated to the same version of RB first. I know this is off topic but we've had success at Actian (we changed our name just last week from Ingres) with a json dump transfer. I didn't perform the migration myself, one of my colleagues did, so I can't offer any thing other than this is worth trying, it worked for us. Of course we moved from version X to version X (not version X to Y). We have previously moved from version X to Y but by using the same database backend, see old thread titled Successful upgrade from Reviewboard 0.9 to 1.0.5.1. For the upgrade from 1.0 to 1.5 series the evolve just worked. Chris -- 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
Re: changing backends Re: Upgrading database/site from 1.0 to 1.6.1
On Mon, Sep 26, 2011 at 9:58 AM, Chris Clark chris.cl...@actian.com wrote: Christian Hammond wrote: [RE changing backend databases] Unofficially, you can do the following: On the old site: rb-site manage /path/to/site dumpdata dbdump.json On the new: . loaddata dbdump.json There are no guarantees it'll work, but give it a try. Note: They will both need to be updated to the same version of RB first. I know this is off topic but we've had success at Actian (we changed our name just last week from Ingres) with a json dump transfer. I didn't perform the migration myself, one of my colleagues did, so I can't offer any thing other than this is worth trying, it worked for us. Of course we moved from version X to version X (not version X to Y). We have previously moved from version X to Y but by using the same database backend, see old thread titled Successful upgrade from Reviewboard 0.9 to 1.0.5.1. For the upgrade from 1.0 to 1.5 series the evolve just worked. Chris Thanks Chris. This comes up often enough that I'm going to add it to the FAQ. Good to hear that others are having success with it. (Before we moved to Django Evolution for our database migrations, this used to be *the* way to upgrade a Review Board database.) Christian -- 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
Upgrading database/site from 1.0 to 1.6.1
Okay, so I have a shiny, new, *working*,* *instance of Reviewboard 1.6.1.
and my plan to migrate my data from my old site was to run rb-site upgrade
on the old site and then copy the newly upgraded database to the new site.
Unfortunately, the database still seem to have a certain amount of 1.0ness
to it and it spat back the Manual server updates required Review Board
page attached. The only thing I did apart from copy over the database was to
change the SECRET_KEY in /conf/settings_local.py. What have I missed? Or am
I going about this all wrong?
I also thought I might as well see the carnage that ensued if I tried to
just get the upgraded old site running and, sure enough, I get a 500 Error
back with the attached Apache error_log.
As always, your help and time are much appreciated,
Sandeep
--
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[Fri Sep 23 13:43:45 2011] [crit] [client 134.244.156.17] (13)Permission
denied: /var/www/reviewboard.test.com/htdocs/.htaccess pcfg_openfile: unable to
check htaccess file, ensure it is readable
[Fri Sep 23 13:43:45 2011] [error] [client 134.244.156.17] mod_python
(pid=29883, interpreter='reviewboard_reviewboard_test_com',
phase='PythonHandler', handler='django.core.handlers.modpython'): Application
error
[Fri Sep 23 13:43:45 2011] [error] [client 134.244.156.17] ServerName:
'cpli6011.net.plm.eds.com'
[Fri Sep 23 13:43:45 2011] [error] [client 134.244.156.17] DocumentRoot:
'/var/www/reviewboard.test.com/htdocs'
[Fri Sep 23 13:43:45 2011] [error] [client 134.244.156.17] URI:
'/error/HTTP_FORBIDDEN.html.var'
[Fri Sep 23 13:43:45 2011] [error] [client 134.244.156.17] Location: '/'
[Fri Sep 23 13:43:45 2011] [error] [client 134.244.156.17] Directory: None
[Fri Sep 23 13:43:45 2011] [error] [client 134.244.156.17] Filename:
'/usr/share/apache2/error/HTTP_FORBIDDEN.html.var'
[Fri Sep 23 13:43:45 2011] [error] [client 134.244.156.17] PathInfo: ''
[Fri Sep 23 13:43:45 2011] [error] [client 134.244.156.17] Traceback (most
recent call last):
[Fri Sep 23 13:43:45 2011] [error] [client 134.244.156.17] File
/usr/lib64/python2.6/site-packages/mod_python/importer.py, line 1537, in
HandlerDispatch\ndefault=default_handler, arg=req, silent=hlist.silent)
[Fri Sep 23 13:43:45 2011] [error] [client 134.244.156.17] File
/usr/lib64/python2.6/site-packages/mod_python/importer.py, line 1229, in
_process_target\nresult = _execute_target(config, req, object, arg)
[Fri Sep 23 13:43:45 2011] [error] [client 134.244.156.17] File
/usr/lib64/python2.6/site-packages/mod_python/importer.py, line 1128, in
_execute_target\nresult = object(arg)
[Fri Sep 23 13:43:45 2011] [error] [client 134.244.156.17] File
/usr/local/lib64/python2.6/site-packages/Django-1.3.1-py2.6.egg/django/core/handlers/modpython.py,
line 212, in handler\nreturn ModPythonHandler()(req)
[Fri Sep 23 13:43:45 2011] [error] [client 134.244.156.17] File
/usr/local/lib64/python2.6/site-packages/Django-1.3.1-py2.6.egg/django/core/handlers/modpython.py,
line 174, in __call__\nself.load_middleware()
[Fri Sep 23 13:43:45 2011] [error] [client 134.244.156.17] File
/usr/local/lib64/python2.6/site-packages/Django-1.3.1-py2.6.egg/django/core/handlers/base.py,
line 39, in load_middleware\nfor middleware_path in
settings.MIDDLEWARE_CLASSES:
[Fri Sep 23 13:43:45 2011] [error] [client 134.244.156.17] File
/usr/local/lib64/python2.6/site-packages/Django-1.3.1-py2.6.egg/django/utils/functional.py,
line 276, in __getattr__\nself._setup()
[Fri Sep 23 13:43:45 2011] [error] [client 134.244.156.17] File
/usr/local/lib64/python2.6/site-packages/Django-1.3.1-py2.6.egg/django/conf/__init__.py,
line 42, in _setup\nself._wrapped = Settings(settings_module)
[Fri Sep 23 13:43:45 2011] [error] [client 134.244.156.17] File
/usr/local/lib64/python2.6/site-packages/Django-1.3.1-py2.6.egg/django/conf/__init__.py,
line 87, in __init__\nmod = importlib.import_module(self.SETTINGS_MODULE)
[Fri Sep 23 13:43:45 2011] [error] [client 134.244.156.17] File
/usr/local/lib64/python2.6/site-packages/Django-1.3.1-py2.6.egg/django/utils/importlib.py,
line 35, in import_module\n__import__(name)
[Fri Sep 23 13:43:45 2011] [error] [client 134.244.156.17] File
/usr/local/lib64/python2.6/site-packages/ReviewBoard-1.6.1-py2.6.egg/reviewboard/settings.py,
line 163, in module\ndependency_error('Unable to read
settings_local.py.')
[Fri Sep 23 13:43:45 2011] [error] [client 134.244.156.17] File
/usr/local/lib64/python2.6/site-packages/ReviewBoard-1.6.1-py2.6.egg/reviewboard/settings.py,
line 150, in dependency_error\nsys.exit(1)
[Fri Sep 23 13:43:45
Re: Upgrading database/site from 1.0 to 1.6.1
By the way, the old site used an SQLite backend. I was going to get access to the legacy code reviews by having an SQLite site alongside the production MySQL site that we'll use going forwards. I notice that We don’t * officially* support converting a database from SQLite to other databases. How about unofficially? Could I get around my problems by importing my data from my 1.0 SQLite db into a 1.6.1 MySQL db? On Fri, Sep 23, 2011 at 3:00 PM, Sandeep Tailor s.tai...@insysion.netwrote: Okay, so I have a shiny, new, *working*,* *instance of Reviewboard 1.6.1. and my plan to migrate my data from my old site was to run rb-site upgrade on the old site and then copy the newly upgraded database to the new site. Unfortunately, the database still seem to have a certain amount of 1.0ness to it and it spat back the Manual server updates required Review Board page attached. The only thing I did apart from copy over the database was to change the SECRET_KEY in /conf/settings_local.py. What have I missed? Or am I going about this all wrong? I also thought I might as well see the carnage that ensued if I tried to just get the upgraded old site running and, sure enough, I get a 500 Error back with the attached Apache error_log. As always, your help and time are much appreciated, Sandeep -- 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
Re: Upgrading database/site from 1.0 to 1.6.1
Hi Sandeep, What manual updates did it show? There are several possible pages beyond database-related updates. Unofficially, you can do the following: On the old site: rb-site manage /path/to/site dumpdata dbdump.json On the new: . loaddata dbdump.json There are no guarantees it'll work, but give it a try. Note: They will both need to be updated to the same version of RB first. Christian On Friday, September 23, 2011, Sandeep Tailor s.tai...@insysion.net wrote: By the way, the old site used an SQLite backend. I was going to get access to the legacy code reviews by having an SQLite site alongside the production MySQL site that we'll use going forwards. I notice that We don’t officially support converting a database from SQLite to other databases. How about unofficially? Could I get around my problems by importing my data from my 1.0 SQLite db into a 1.6.1 MySQL db? On Fri, Sep 23, 2011 at 3:00 PM, Sandeep Tailor s.tai...@insysion.net wrote: Okay, so I have a shiny, new, working, instance of Reviewboard 1.6.1. and my plan to migrate my data from my old site was to run rb-site upgrade on the old site and then copy the newly upgraded database to the new site. Unfortunately, the database still seem to have a certain amount of 1.0ness to it and it spat back the Manual server updates required Review Board page attached. The only thing I did apart from copy over the database was to change the SECRET_KEY in /conf/settings_local.py. What have I missed? Or am I going about this all wrong? I also thought I might as well see the carnage that ensued if I tried to just get the upgraded old site running and, sure enough, I get a 500 Error back with the attached Apache error_log. As always, your help and time are much appreciated, Sandeep -- 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 reviewboard%2bunsubscr...@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
