After some wrangling, I'm still stranded and not quite sure how to get past this. Appreciate any help.
On Friday, September 16, 2011 11:48:13 AM UTC-7, Christian Hammond wrote: > > Thanks for the info Joe. Glad 16.0 to 1.6.1 was more smooth. I'm not sure > what caused the problems with the upgrade to 1.6.0 (those haven't been > showing up in our regression tests), but we'll continue to look into it. > > Christian > > -- > Christian Hammond - chi...@chipx86.com > Review Board - http://www.reviewboard.org > VMware, Inc. - http://www.vmware.com > > > On Fri, Sep 16, 2011 at 8:43 AM, Joe Campbell <joseph.r...@gmail.com>wrote: > >> I did eventually make it past this issue by physically making the >> modifications to the postgres database by hand. The evolution then >> completed and I was able to 'revert' any changes I had done and >> everything worked. >> >> After this was all said and done - upgrading from 1.6.0 to 1.6.1, >> 'Just worked' without needing any special intervention from me. >> >> Joe >> >> On Sep 11, 4:14 pm, Christian Hammond <chi...@chipx86.com> wrote: >> > Which 1.5? >> > >> > Christian >> > >> > -- >> > Christian Hammond - chi...@chipx86.com >> > Review Board -http://www.reviewboard.org >> > VMware, Inc. -http://www.vmware.com >> > >> > On Sun, Sep 11, 2011 at 1:02 PM, Joe Campbell >> > <joseph.r...@gmail.com>wrote: >> > >> > >> > >> > >> > >> > >> > >> > > Was upgrading from base 1.5 release to 1.6 with a postgres DB. I did >> > > eventually get the evolutions to work by renaming existing columns and >> > > dropping at least one empty table. This allowed the evolutions to >> complete >> > > and I was able to get the site back up and running. >> > >> > > Joe >> > >> > > On Sat, Sep 10, 2011 at 3:43 AM, Christian Hammond < >> chi...@chipx86.com>wrote: >> > >> > >> Hi Joe, >> > >> > >> Sorry, this got lost in a flood of e-mails. >> > >> > >> What version were you upgrading from? >> > >> > >> What type of database? >> > >> > >> Christian >> > >> > >> -- >> > >> Christian Hammond - chi...@chipx86.com >> > >> Review Board -http://www.reviewboard.org >> > >> VMware, Inc. -http://www.vmware.com >> > >> > >> On Thu, Sep 8, 2011 at 1:05 PM, Joe Campbell <joseph.r...@gmail.com >> > >> > wrote: >> > >> > >>> Running rb-site upgrade /var/www/cim-review after an easy_install -U >> > >>> ReviewBoard resulted in this: >> > >> > >>> Rebuilding directory structure >> > >>> Updating database. This may take a while. >> > >>> /usr/lib/python2.6/site-packages/Django-1.3-py2.6.egg/django/db/ >> > >>> __init__.py:60: DeprecationWarning: Short names for ENGINE in >> database >> > >>> configurations are deprecated. Prepend default.ENGINE with >> > >>> 'django.db.backends.' >> > >>> DeprecationWarning >> > >>> Creating tables ... >> > >>> There are unapplied evolutions for sessions. >> > >>> There are unapplied evolutions for accounts. >> > >>> There are unapplied evolutions for diffviewer. >> > >>> There are unapplied evolutions for reviews. >> > >>> There are unapplied evolutions for scmtools. >> > >>> Project signature has changed - an evolution is required >> > >>> Installing custom SQL ... >> > >>> Installing indexes ... >> > >>> No fixtures found. >> > >>> >> /usr/lib/python2.6/site-packages/pycrypto-2.3-py2.6-linux-x86_64.egg/ >> > >>> Crypto/Util/randpool.py:40: RandomPool_DeprecationWarning: This >> > >>> application uses RandomPool, which is BROKEN in older releases. See >> > >>>http://www.pycrypto.org/randpool-broken >> > >>> RandomPool_DeprecationWarning) >> > >>> Error: Error applying evolution: column "basedir" of relation >> > >>> "diffviewer_diffset" already exists >> > >> > >>> And now my ReviewBoard Instance is complaining the DB is broken. >> > >>> HELP? >> > >> > >>> -- >> > >>> Want to help the Review Board project? Donate today at >> > >>>http://www.reviewboard.org/donate/ >> > >>> Happy user? Let us know athttp://www.reviewboard.org/users/ >> > >>> -~----------~----~----~----~------~----~------~--~--- >> > >>> To unsubscribe from this group, send email to >> > >>> reviewboard...@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 athttp://www.reviewboard.org/users/ >> > >> -~----------~----~----~----~------~----~------~--~--- >> > >> To unsubscribe from this group, send email to >> > >> reviewboard...@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 athttp://www.reviewboard.org/users/ >> > > -~----------~----~----~----~------~----~------~--~--- >> > > To unsubscribe from this group, send email to >> > > reviewboard...@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...@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
