Sorry, scratch that. I'm able to reproduce this when going from beta 1 to
RC1 as well. It has to do with the is_profile. Looking into it. It *does*
have an evolution file, but it appears that it's not being taken into
account.

Christian

-- 
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com


On Wed, Jun 29, 2011 at 1:31 PM, Christian Hammond <chip...@chipx86.com>wrote:

> So what I'm seeing is that some of these evolutions that have been applied
> are recorded as having already been applied. That most often happens when
> you've done an upgrade, then tried reverting the schema for some reason
> (perhaps to downgrade) but never erased the evolution history. You say the
> database wasn't modified, but did anything ever happen beyond just upgrading
> from one release to another?
>
> What database are you using?
>
> What version of Review Board did you have installed prior to 1.6 beta 1?
>
> Christian
>
> --
> Christian Hammond - chip...@chipx86.com
>
> Review Board - http://www.reviewboard.org
> VMware, Inc. - http://www.vmware.com
>
>
> On Wed, Jun 29, 2011 at 1:02 PM, martin <martin.don...@gmail.com> wrote:
>
>> Thanks Christian.
>>
>> Screenshot: http://dl.dropbox.com/u/9410307/evolutions.PNG
>>
>> #----- Evolution for sessions
>> from django_evolution.mutations import *
>> from django.db import models
>>
>> MUTATIONS = [
>>    ChangeField('Session', 'expire_date', initial=None, db_index=True)
>> ]
>> #----------------------
>> #----- Evolution for accounts
>> from django_evolution.mutations import *
>> from django.db import models
>>
>> MUTATIONS = [
>>    AddField('Profile', 'is_private', models.BooleanField,
>> initial=False)
>> ]
>> #----------------------
>> #----- Evolution for reviews
>> from django_evolution.mutations import *
>> from django.db import models
>>
>> MUTATIONS = [
>>    AddField('Comment', 'issue_opened', models.BooleanField,
>> initial=False),
>>    AddField('Comment', 'issue_status', models.CharField,
>> max_length=1, null=True, db_index=True),
>>    AddField('Group', 'local_site', models.ForeignKey, null=True,
>> related_model='site.LocalSite'),
>>    AddField('Group', 'incoming_request_count', models.CounterField,
>> null=True),
>>    AddField('Group', 'visible', models.BooleanField, initial=True),
>>    AddField('Group', 'invite_only', models.BooleanField,
>> initial=False),
>>    ChangeField('Group', 'name', initial=None, unique=False),
>>    AddField('Review', 'file_attachment_comments',
>> models.ManyToManyField,
>> related_model='reviews.FileAttachmentComment'),
>>    AddField('ReviewRequestDraft', 'inactive_file_attachments',
>> models.ManyToManyField, related_model='attachments.FileAttachment'),
>>    AddField('ReviewRequestDraft', 'file_attachments',
>> models.ManyToManyField, related_model='attachments.FileAttachment'),
>>    AddField('ReviewRequest', 'inactive_file_attachments',
>> models.ManyToManyField, related_model='attachments.FileAttachment'),
>>    AddField('ReviewRequest', 'local_site', models.ForeignKey,
>> null=True, related_model='site.LocalSite'),
>>    AddField('ReviewRequest', 'local_id', models.IntegerField,
>> null=True),
>>    AddField('ReviewRequest', 'file_attachments',
>> models.ManyToManyField, related_model='attachments.FileAttachment'),
>>    AddField('DefaultReviewer', 'local_site', models.ForeignKey,
>> null=True, related_model='site.LocalSite'),
>>    AddField('ScreenshotComment', 'issue_opened', models.BooleanField,
>> initial=False),
>>    AddField('ScreenshotComment', 'issue_status', models.CharField,
>> max_length=1, null=True, db_index=True)
>> ]
>> #----------------------
>> #----- Evolution for scmtools
>> from django_evolution.mutations import *
>> from django.db import models
>>
>> MUTATIONS = [
>>    AddField('Repository', 'review_groups', models.ManyToManyField,
>> related_model='reviews.Group'),
>>    AddField('Repository', 'local_site', models.ForeignKey, null=True,
>> related_model='site.LocalSite'),
>>    AddField('Repository', 'public', models.BooleanField,
>> initial=True),
>>    AddField('Repository', 'users', models.ManyToManyField,
>> related_model='auth.User'),
>>    ChangeField('Repository', 'path', initial=None, unique=False),
>>    ChangeField('Repository', 'name', initial=None, unique=False)
>> ]
>> #----------------------
>> Trial evolution successful.
>> Run './manage.py evolve --hint --execute' to apply evolution.
>>
>>
>> On Jun 29, 12:20 pm, Christian Hammond <chip...@chipx86.com> wrote:
>> > Those were added before beta 1, but I think the error may be misleading.
>> It
>> > mentions "sessions", which is Django-supplied.
>> >
>> > Can you run:
>> >
>> >     $ rb-site manage /path/to/site evolve -- --hint
>> >
>> > (Do not run --hint --execute if anyone tells you to)
>> >
>> > Show me the results of that.
>> >
>> > Then, go into the admin UI -> Database -> Evolutions and screenshot that
>> for
>> > me. I need to see the entire list. You can send that privately, but it
>> > shouldn't have any confidential info.
>> >
>> > Christian
>> >
>> > --
>> > Christian Hammond - chip...@chipx86.com
>> > Review Board -http://www.reviewboard.org
>> > VMware, Inc. -http://www.vmware.com
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> > On Wed, Jun 29, 2011 at 11:54 AM, martin <martin.don...@gmail.com>
>> wrote:
>> > > When I run rb-site upgrade /my/site I get the following:
>> >
>> > > ===
>> > > Rebuilding directory structure
>> > > Updating database. This may take a while.
>> > > Creating tables ...
>> > > Upgrading Review Board from 1.6 beta 1 to 1.6 RC1
>> > > There are unapplied evolutions for sessions.
>> > > There are unapplied evolutions for accounts.
>> > > There are unapplied evolutions for reviews.
>> > > Project signature has changed - an evolution is required
>> > > Installing custom SQL ...
>> > > Installing indexes ...
>> > > No fixtures found.
>> > > /usr/local/lib/python2.6/dist-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.
>> > > Seehttp://www.pycrypto.org/randpool-broken
>> > >  RandomPool_DeprecationWarning)
>> > > 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:
>> > > In model reviews.DefaultReviewer:
>> > >    Field 'local_site' has been added
>> > > In model reviews.ReviewRequest:
>> > >    Field 'local_site' has been added
>> > >    Field 'local_id' has been added
>> > > In model reviews.Group:
>> > >    Field 'local_site' has been added
>> > >    Field 'incoming_request_count' has been added
>> > >    Field 'visible' has been added
>> > >    Field 'invite_only' has been added
>> > >    In field 'name':
>> > >        Property 'unique' has changed
>> > > In model scmtools.Repository:
>> > >    Field 'review_groups' has been added
>> > >    Field 'local_site' has been added
>> > >    Field 'public' has been added
>> > >    Field 'users' has been added
>> > >    In field 'path':
>> > >        Property 'unique' has changed
>> > >    In field 'name':
>> > >        Property 'unique' has changed
>> > > Error: Your models contain changes that Django Evolution cannot
>> > > resolve automatically.
>> > > ===
>> >
>> > > I haven't made any modifications to the DB structure myself between
>> > > beta1 and rc1. This upgrade did also include and upgrade from django
>> > > 1.2.5 to django 1.3, not sure if that effects anything. Can anyone
>> > > suggest how I would go about resolving this?
>> >
>> > > --
>> > > 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+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
>>
>
>

-- 
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

Reply via email to