I decided to try this from a fresh install of lenny in a vm. This install has never seen a reviewboard install. I hope was that in the VM the migration would work, then I could just move my db back to my production machine and it would have all the right columns.
This did not work though. After doing an install to the VM according to the direction on GettingStarted I copied my production db over the fresh reviewboard.db. I then ran rb-site upgrade /var/www/site and copied the resulting reviewboard.db back to my machine. I ran sqlitebrowser and the scmtools_repository table had no encoding column. I altered the table to have an encoding varchar(32) column but that cropped up another missing column error so I stopped there. Mike On Feb 22, 9:33 pm, Mike <mcass...@gmail.com> wrote: > To expand on how I re-installed django-evolution, after rm'ing I ran: > > m...@debian:/usr/lib/python2.5/site-packages$ sudo easy_install > ReviewBoard > Searching for ReviewBoard > Best match: ReviewBoard 1.0alpha4 > Processing ReviewBoard-1.0alpha4-py2.5.egg > ReviewBoard 1.0alpha4 is already the active version in easy- > install.pth > Installing rb-site script to /usr/bin > > Using /usr/lib/python2.5/site-packages/ReviewBoard-1.0alpha4-py2.5.egg > Processing dependencies for ReviewBoard > Searching for django-evolution > Readinghttp://downloads.review-board.org/mirror/ > Readinghttp://downloads.review-board.org/releases/ > Best match: django-evolution 0.0.0 > Downloadinghttp://downloads.review-board.org/mirror/django_evolution-0.0.0.tar.gz > Processing django_evolution-0.0.0.tar.gz > Running django_evolution-0.0.0/setup.py -q bdist_egg --dist-dir /tmp/ > easy_install-1lGVx2/django_evolution-0.0.0/egg-dist-tmp-AlTaBk > zip_safe flag not set; analyzing archive contents... > django_evolution.evolve: module references __file__ > Adding django-evolution 0.0.0 to easy-install.pth file > > Installed /usr/lib/python2.5/site-packages/django_evolution-0.0.0- > py2.5.egg > Finished processing dependencies for ReviewBoard > > On Feb 22, 9:28 pm, Mike <mcass...@gmail.com> wrote: > > > I removed django-evolution by rm'ing the dir from site-packages. It's > > not clear to me whether my system is using python2.4 or python2.5, > > just a side-note. I'm pretty sure reviewboard was installed to > > python2.4 before and now it seems to be using python2.5. > > > Currently there is no django-evolution dir in /usr/lib/python2.4/site- > > packages. In /usr/lib/python2.5/site-packages I have: > > > m...@debian:/usr/lib/python2.5/site-packages$ ls -la > > django_evolution-0.0.0-py2.5.egg/ > > total 16 > > drwxr-xr-x 4 root root 4096 2009-02-22 20:27 . > > drwxr-xr-x 23 root root 4096 2009-02-22 20:40 .. > > drwxr-xr-x 5 root root 4096 2009-02-22 20:27 django_evolution > > drwxr-xr-x 2 root root 4096 2009-02-22 20:27 EGG-INFO > > > m...@debian:/usr/lib/python2.5/site-packages$ cat > > django_evolution-0.0.0-py2.5.egg/EGG-INFO/PKG-INFO > > Metadata-Version: 1.0 > > Name: django-evolution > > Version: 0.0.0 > > Summary: An implementation of schema evolution for the Django web > > framework. > > Home-page:http://code.google.com/p/django-evolution/ > > Author: Ben Khoo > > Author-email: khoo...@westnet.com.au > > License: UNKNOWN > > Description: UNKNOWN > > Platform: UNKNOWN > > > Version 0.0.0 is not inspiring, is this a good way to check whether I > > have a good version or not? > > > Mike > > > On Feb 22, 9:17 pm, Christian Hammond <chip...@chipx86.com> wrote: > > > > How did you attempt the reinstall? Since django_evolution has no version, > > > simply doing an easy_install -U django_evolution isn't enough. You'll have > > > to go in and delete your old copy in your Python's site-packages directory > > > and then install it. > > > > I'm looking to work around this by stamping nightly builds of > > > django_evolution soon. > > > > Christian > > > > -- > > > Christian Hammond - chip...@chipx86.com > > > Review Board -http://www.review-board.org > > > VMware, Inc. -http://www.vmware.com > > > > On Sun, Feb 22, 2009 at 7:07 PM, Mike <mcass...@gmail.com> wrote: > > > > > I was using a 0.9 version of review board and installed it according > > > > to the instructions on GettingStarted. I downloaded the code using > > > > the "nightlies" repository. I want to preserve my old database of > > > > reviews so I copied (using cp) the reviewboard.sqlite file onto the > > > > freshly installed reviewboard.db. > > > > > I then ran rb-site --upgrade /var/www/site and output: > > > > > m...@debian:/var/www/site$ sudo rb-site upgrade /var/www/site/ > > > > Rebuilding directory structure > > > > Updating database > > > > Creating table siteconfig_siteconfiguration > > > > Creating table changedescs_changedescription > > > > Creating table django_project_version > > > > Creating table django_evolution > > > > *** Migrating settings from settings_local.py to the database. > > > > *** If you have previously configured Review Board through a > > > > *** settings_local.py file, please ensure that the migration > > > > *** was successful by verifying your settings at > > > > ***http://192.168.0.101/admin/settings/ > > > > Installing baseline version > > > > Evolutions in diffviewer baseline: add_parent_diffs > > > > Evolutions in reviews baseline: change_descriptions > > > > Evolutions in scmtools baseline: bugzilla_url_charfield > > > > Installing index for siteconfig.SiteConfiguration model > > > > Installing index for django_evolution.Evolution model > > > > Installing json fixture 'initial_data' from '/usr/lib/python2.5/site- > > > > packages/ReviewBoard-1.0alpha4-py2.5.egg/reviewboard/scmtools/ > > > > fixtures'. > > > > Installed 6 object(s) from 1 fixture(s) > > > > No evolution required. > > > > > Now when I site the site it works, but if I hit anything related to > > > > reviews I get (after settings debug to True in settings_local.py): > > > > > OperationalError at /r/new/ > > > > > no such column: scmtools_repository.encoding > > > > > I open reviewboard.db with sqlitebrowser I clearly see that the > > > > encoding column does not exist. When I view sqlitebrowser on the > > > > fresh install I see that encoding column does exist. > > > > > There was a prior post suggesting that the user did not have django- > > > > evolution installed properly and I have tried reinstalling that which > > > > seemed to go right. > > > > > Some how the column is not being migrated when I copy the old db over > > > > the new one. Suggestions? Thanks. > > > > > Mike --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "reviewboard" group. To post to this group, send email to reviewboard@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
