I reported success with the new django-evolution in a different thread, but 
I'm replying again here just to get all the information in one place.  The 
conversion of my 1.5 database to 1.7 took a long time - possibly hours.  I 
monitored it for about an hour and then just left it for the weekend. When 
I came back on Monday it had successfully finished. Our database is about 
6GB in size running on a MySQL server.  Hope that helps.

Thanks for the patch Chris.

--Steve

On Saturday, March 9, 2013 2:44:59 PM UTC-8, Christian Hammond wrote:
>
> I haven't received enough replies to be able to say. Having you test this 
> would really help.
>
> Would you be willing to make a backup of your database, then install the 
> Django Evolution package from 
> http://downloads.reviewboard.org/temp/django-evolution/? You'd need to 
> attempt the upgrade again and then test out the site a bit, make sure 
> nothing is broken (including commenting on file attachments).
>
> Christian
>
> -- 
> Christian Hammond - chi...@chipx86.com <javascript:>
> Review Board - http://www.reviewboard.org
> VMware, Inc. - http://www.vmware.com 
>
> On Mar 9, 2013, at 2:37 PM, tex.b...@gmail.com <javascript:> wrote:
>
> Hi,
> was this experiment successful ?
> Like some others, I took a snapshot of a working 1.5.5 installation from 
> Centos 5.5, copied it to a Centos 6.3 machine, and upgraded to 1.6.15, then 
> to 1.7.6.
> That all took 2 months, due to various issues and lack of focus. Today I 
> took another snapshot of my working 1.5.5 installation, and tried to apply 
> that. I dropped the working but out-of-date reviewboard table in the 1.7.6 
> installation, then restored the current .sql file from the 1.5.5 release; 
> then did 
> "/usr/bin/python" "/usr/bin/rb-site" upgrade "/var/www/reviewboard". That 
> produced a site which just sayd 'Something broke." The output from the 
> upgrade command is:
> Error: Model 'reviews.FileAttachmentComment' already has a field named 
> 'extra_data'
> 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.5.5 to 1.7.6
> There are unapplied evolutions for auth.
> There are unapplied evolutions for accounts.
> There are unapplied evolutions for changedescs.
> There are unapplied evolutions for diffviewer.
> There are unapplied evolutions for reviews.
> There are unapplied evolutions for scmtools.
> Adding baseline version for new models
> 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
>
> I expect I'm doing something fundamentally wrong, but this seems to be a 
> common usage model, so perhaps someone can steer me straight ?
> Thanks,
>
>
>
> On Friday, March 1, 2013 9:58:34 AM UTC-8, Steve wrote:
>>
>> I can also test it on my sandbox which is currently in this state.
>>
>> --steve
>>
>>
>> On Wednesday, February 27, 2013 12:05:31 AM UTC-8, Christian Hammond 
>> wrote:
>>>
>>> Hi again,
>>>
>>> I actually think I may have a fix for Django Evolution, but I will need 
>>> volunteers to test. I'll be sending out an e-mail with instructions shortly.
>>>
>>> Christian
>>>
>>> -- 
>>> Christian Hammond - chi...@chipx86.com
>>> Review Board - http://www.reviewboard.org
>>> VMware, Inc. - http://www.vmware.com 
>>>
>>> On Feb 26, 2013, at 9:00 PM, Nachiketh G <nach...@gmail.com> wrote:
>>>
>>> Hi Sebastien/Christian,
>>> I tried the upgrading from a 1.0 release of RB to 1.7.x and ran into the 
>>> exact same error when I did a "rb-site upgrade". 
>>> *Error: Model 'reviews.FileAttachmentComment' already has a field named 
>>> 'extra_data'*
>>>
>>> Were you guys able to find a solution to this problem? Do let me know.
>>> Thanks & Regards,
>>> Nachiketh
>>>
>>>
>>> On Thursday, 27 December 2012 20:45:22 UTC+5:30, S├ębastien Douche wrote:
>>>>
>>>> Hi, 
>>>> I'm trying to upgrade RB to the last version: 
>>>>
>>>> rd1:~/ReviewBoard-1.7.1# rb-site upgrade /srv/reviewboard 
>>>> 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> ------------------ 
>>>> /usr/local/lib/python2.6/dist-packages/Djblets-0.7.7-py2.6.egg/djblets/gravatars/__init__.py:26:
>>>>  
>>>>
>>>> DeprecationWarning: the md5 module is deprecated; use hashlib instead 
>>>>   from md5 import md5 
>>>> 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.5 to 1.7.1 
>>>> There are unapplied evolutions for auth. 
>>>> There are unapplied evolutions for sessions. 
>>>> There are unapplied evolutions for accounts. 
>>>> There are unapplied evolutions for changedescs. 
>>>> There are unapplied evolutions for diffviewer. 
>>>> There are unapplied evolutions for reviews. 
>>>> There are unapplied evolutions for scmtools. 
>>>> Adding baseline version for new models 
>>>> 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 
>>>> Error: Model 'reviews.FileAttachmentComment' already has a field named 
>>>> 'extra_data' 
>>>>
>>>> On IHM: 
>>>>
>>>> DatabaseError at /dashboard/ 
>>>> (1054, "Unknown column 'accounts_profile.is_private' in 'field list'") 
>>>>
>>>> Any ideas? 
>>>>
>>>>
>>>>
>>>>
>>>> -- 
>>>> Sebastien Douche <sdo...@gmail.com> 
>>>> Twitter: @sdouche / G+: +sdouche 
>>>>
>>>
>>> -- 
>>> 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
>>> --- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "reviewboard" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to reviewboard...@googlegroups.com.
>>> For more options, visit https://groups.google.com/groups/opt_out.
>>>  
>>>  
>>>
>>>
>>>
>

-- 
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
--- 
You received this message because you are subscribed to the Google Groups 
"reviewboard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to