Hi Zach, I know this isn't going quick. We had a big upgrade to RBCommons.com to prepare for and execute, and a number of premium support tickets we've been dealing with, so I'm behind on the community list.
I took a look at the dumps, but unfortunately they're not useful to me. I'll need actual raw SQL dumps that I can directly import into a Postgres database. Would you be able to provide an importable SQL dump? - Christian -- Christian Hammond - [email protected] Review Board - http://www.reviewboard.org Beanbag, Inc. - http://www.beanbaginc.com On Thu, Aug 21, 2014 at 3:03 PM, Zach Auclair <[email protected]> wrote: > Christian, > > I've attached the data that you requested. > > -Zach > > > On Thu, Aug 21, 2014 at 4:41 PM, Christian Hammond < > [email protected]> wrote: > >> Hi Zach, >> >> Sorry, I haven’t had a chance yet. >> >> I just glanced through and the schema does look correct, as does the list >> of applied evolutions. Can you get me the contents of your >> django_project_version and django_evolution tables? That’ll give me a >> better understanding of how Django Evolution thinks the world looks. >> >> Christian >> >> -- >> Christian Hammond - [email protected] >> Review Board - http://www.reviewboard.org >> Beanbag, Inc. - http://www.beanbaginc.com >> >> On August 21, 2014 at 1:24:01 PM, Zach Auclair ([email protected]) wrote: >> >> Hey Christian, >> >> Have you had a chance to look into this? Is there any other information I >> can get you? >> >> -Zach >> >> >> >> On Fri, Aug 15, 2014 at 10:11 PM, Zach Auclair <[email protected]> wrote: >> >>> Hi Chris, >>> >>> The output of the "list-evolutions" command is actually included in my >>> last paragraph in the original post - see "*... in "list-evolutions" >>> form.*" >>> >>> I have attached the current schema generated by `pg_dump --schema-only >>> ...`. >>> >>> >>> On Fri, Aug 15, 2014 at 4:37 PM, Christian Hammond < >>> [email protected]> wrote: >>> >>>> Hmm, that shouldn’t be happening. Can you run this and show me what >>>> you see: >>>> >>>> $ rb-site manage /path/to/site list-evolutions >>>> >>>> Also, can you dump the schema of your database and attach it? >>>> >>>> - Christian >>>> >>>> -- >>>> Christian Hammond - [email protected] >>>> Review Board - http://www.reviewboard.org >>>> Beanbag, Inc. - http://www.beanbaginc.com >>>> >>>> On August 15, 2014 at 12:11:45 PM, Zach ([email protected]) wrote: >>>> >>>> I'm trying to "rb-site upgrade" an old 1.5.5 database to 2.0.5. >>>> >>>> *This fails with:* >>>> >>>> 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 ... >>>> There are unapplied evolutions for auth. >>>> There are unapplied evolutions for contenttypes. >>>> 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. >>>> Project signature has changed - an evolution is required >>>> Installing custom SQL ... >>>> Installing indexes ... >>>> Installed 0 object(s) from 0 fixture(s) >>>> 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: >>>> The application markup has been deleted >>>> In model reviews.DefaultReviewer: >>>> In field 'repository': >>>> Property 'null' has changed >>>> In model reviews.ReviewRequest: >>>> In field 'repository': >>>> Property 'null' has changed >>>> CommandError: Your models contain changes that Django Evolution cannot >>>> resolve automatically. >>>> >>>> >>>> *The suggested --hint's are:* >>>> >>>> #----- Evolution for auth >>>> from django_evolution.mutations import ChangeMeta, DeleteModel >>>> >>>> >>>> MUTATIONS = [ >>>> ChangeMeta('Permission', 'unique_together', ((u'content_type', >>>> u'codename'),)), >>>> DeleteModel('Message') >>>> ] >>>> #---------------------- >>>> #----- Evolution for contenttypes >>>> from django_evolution.mutations import ChangeMeta >>>> >>>> >>>> MUTATIONS = [ >>>> ChangeMeta('ContentType', 'unique_together', (('app_label', >>>> 'model'),)) >>>> ] >>>> #---------------------- >>>> #----- Evolution for sessions >>>> from django_evolution.mutations import ChangeField >>>> >>>> >>>> MUTATIONS = [ >>>> ChangeField('Session', 'expire_date', initial=None, db_index=True) >>>> ] >>>> #---------------------- >>>> #----- Evolution for accounts >>>> from django_evolution.mutations import AddField, ChangeMeta, DeleteField >>>> from django.db import models >>>> from djblets.db.fields import JSONField >>>> >>>> >>>> MUTATIONS = [ >>>> AddField('Profile', 'should_send_email', models.BooleanField, >>>> initial=True), >>>> AddField('Profile', 'timezone', models.CharField, initial=u'UTC', >>>> max_length=30), >>>> AddField('Profile', 'open_an_issue', models.BooleanField, >>>> initial=True), >>>> AddField('Profile', 'extra_data', JSONField, null=True), >>>> AddField('Profile', 'show_closed', models.BooleanField, >>>> initial=True), >>>> AddField('Profile', 'is_private', models.BooleanField, >>>> initial=False), >>>> DeleteField('Profile', 'show_submitted'), >>>> ChangeMeta('ReviewRequestVisit', 'unique_together', ((u'user', >>>> u'review_request'),)) >>>> ] >>>> #---------------------- >>>> #----- Evolution for changedescs >>>> from django_evolution.mutations import AddField >>>> from django.db import models >>>> >>>> >>>> MUTATIONS = [ >>>> AddField('ChangeDescription', 'rich_text', models.BooleanField, >>>> initial=True) >>>> ] >>>> #---------------------- >>>> CommandError: Cannot use hinted evolution: AddField or ChangeField >>>> mutation for 'FileDiff.status' in 'diffviewer' requires user-specified >>>> initial value. >>>> >>>> *The completed evolutions are:* >>>> >>>> reviewboard=> select * from django_evolution; >>>> id | version_id | app_label | label >>>> >>>> ----+------------+-------------+--------------------------------------------- >>>> 1 | 4 | diffviewer | add_parent_diffs >>>> 2 | 4 | reviews | change_descriptions >>>> 3 | 4 | scmtools | bugzilla_url_charfield >>>> 4 | 5 | attachments | file_attachment_orig_filename >>>> 5 | 5 | attachments | file_attachment_file_max_length_512 >>>> 6 | 5 | attachments | file_attachment_repo_info >>>> 7 | 5 | attachments | file_attachment_repo_path_no_index >>>> 8 | 5 | attachments | >>>> file_attachment_repo_revision_max_length_64 >>>> 9 | 5 | site | localsite_public >>>> 10 | 5 | hostingsvcs | account_hosting_url >>>> 11 | 5 | hostingsvcs | account_hosting_url_max_length_255 >>>> 12 | 5 | hostingsvcs | account_unique_together_baseline >>>> (12 rows) >>>> >>>> reviewboard=> \d django_evolution >>>> Table "public.django_evolution" >>>> Column | Type | >>>> Modifiers >>>> >>>> ------------+------------------------+--------------------------------------------------------------- >>>> id | integer | not null default >>>> nextval('django_evolution_id_seq'::regclass) >>>> version_id | integer | not null >>>> app_label | character varying(200) | not null >>>> label | character varying(100) | not null >>>> Indexes: >>>> "django_evolution_pkey" PRIMARY KEY, btree (id) >>>> "django_evolution_version_id" btree (version_id) >>>> Foreign-key constraints: >>>> "django_evolution_version_id_fkey" FOREIGN KEY (version_id) >>>> REFERENCES django_project_version(id) DEFERRABLE INITIALLY DEFERRED >>>> >>>> reviewboard=> >>>> >>>> *... in "list-evolutions" form:* >>>> >>>> Applied evolutions for 'attachments': >>>> file_attachment_orig_filename >>>> file_attachment_file_max_length_512 >>>> file_attachment_repo_info >>>> file_attachment_repo_path_no_index >>>> file_attachment_repo_revision_max_length_64 >>>> >>>> Applied evolutions for 'diffviewer': >>>> add_parent_diffs >>>> >>>> Applied evolutions for 'hostingsvcs': >>>> account_hosting_url >>>> account_hosting_url_max_length_255 >>>> account_unique_together_baseline >>>> >>>> Applied evolutions for 'reviews': >>>> change_descriptions >>>> >>>> Applied evolutions for 'scmtools': >>>> bugzilla_url_charfield >>>> >>>> Applied evolutions for 'site': >>>> localsite_public >>>> >>>> >>>> >>>> -- >>>> Get the Review Board Power Pack at >>>> http://www.reviewboard.org/powerpack/ >>>> --- >>>> Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ >>>> --- >>>> Happy user? Let us know at http://www.reviewboard.org/users/ >>>> --- >>>> 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 [email protected]. >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>>> >>> >> > -- > Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ > --- > Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ > --- > Happy user? Let us know at http://www.reviewboard.org/users/ > --- > 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 [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ --- Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ --- Happy user? Let us know at http://www.reviewboard.org/users/ --- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
