Re: Problems upgrading to 2.0.13 and 2.0.15
That fixed it. Many Thanks! On Friday, April 17, 2015 at 2:05:03 PM UTC-7, Christian Hammond wrote: > > Hi Daniel, > > Sorry, I've been pretty swamped. > > First, make a backup of your database. Then, try: > > DELETE FROM django_project_version WHERE id=4; > > Then perform the upgrade again. > > Christian > > -- > Christian Hammond - chi...@chipx86.com > Review Board - http://www.reviewboard.org > Beanbag, Inc. - http://www.beanbaginc.com > > On Fri, Apr 17, 2015 at 10:29 AM, Daniel Dominguez > wrote: > >> Any update here? >> >> >> On Friday, March 20, 2015 at 1:29:07 PM UTC-7, Daniel Dominguez wrote: >>> >>> Running --hint --evolve had not been done before. It was just my >>> experimenting after seeing this issue (with a current backup of the db >>> first of course). >>> >>> Anyhow, I've attached the sql dump you requested. >>> >>> Thanks! >>> >>> On Friday, March 20, 2015 at 8:28:36 AM UTC-7, Daniel Dominguez wrote: When I performed the upgrade form 2.0.12 to 2.0.13, the site-upgrade failed. It didn't seem to break our reviewboard instance, so I just ignored it at the time. I recently upgraded to 2.0.15, and the result is the same. Again, our reviewboard server seems to be fine, but this is starting to make me nervous. -- -- Creating tables ... 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: In model reviews.ReviewRequest: Field 'description_rich_text' has been added Field 'testing_done_rich_text' has been added In model reviews.Review: Field 'body_top_rich_text' has been added Field 'body_bottom_rich_text' has been added In model reviews.ReviewRequestDraft: Field 'description_rich_text' has been added Field 'testing_done_rich_text' has been added In model accounts.Profile: Field 'default_use_rich_text' has been added CommandError: Your models contain changes that Django Evolution cannot resolve automatically. I've trying running evolve -- --hint --execute, but that fails with the following CommandError: Error applying evolution: (1060, "Duplicate column name 'default_use_rich_text'") I've checked that I have the latest django_evolution installed for my platform (0.7.4). This is running on a MySql database. It seems like the evolution is trying to add columns that already exist. Maybe a version table didn't get incremented in the prior evolution? Any hints on how I can troubleshoot this? -- >> Supercharge your Review Board with Power Pack: >> https://www.reviewboard.org/powerpack/ >> Want us to host Review Board for you? Check out RBCommons: >> https://rbcommons.com/ >> Happy user? Let us know! https://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 reviewboard...@googlegroups.com . >> For more options, visit https://groups.google.com/d/optout. >> > > -- Supercharge your Review Board with Power Pack: https://www.reviewboard.org/powerpack/ Want us to host Review Board for you? Check out RBCommons: https://rbcommons.com/ Happy user? Let us know! https://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 reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Problems upgrading to 2.0.13 and 2.0.15
Hi Daniel, Sorry, I've been pretty swamped. First, make a backup of your database. Then, try: DELETE FROM django_project_version WHERE id=4; Then perform the upgrade again. Christian -- Christian Hammond - chip...@chipx86.com Review Board - http://www.reviewboard.org Beanbag, Inc. - http://www.beanbaginc.com On Fri, Apr 17, 2015 at 10:29 AM, Daniel Dominguez < daniel.j.doming...@gmail.com> wrote: > Any update here? > > > On Friday, March 20, 2015 at 1:29:07 PM UTC-7, Daniel Dominguez wrote: >> >> Running --hint --evolve had not been done before. It was just my >> experimenting after seeing this issue (with a current backup of the db >> first of course). >> >> Anyhow, I've attached the sql dump you requested. >> >> Thanks! >> >> On Friday, March 20, 2015 at 8:28:36 AM UTC-7, Daniel Dominguez wrote: >>> >>> When I performed the upgrade form 2.0.12 to 2.0.13, the site-upgrade >>> failed. It didn't seem to break our reviewboard instance, so I just >>> ignored it at the time. I recently upgraded to 2.0.15, and the result is >>> the same. Again, our reviewboard server seems to be fine, but this is >>> starting to make me nervous. >>> >>> >>> -- -- >>> Creating tables ... >>> 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: >>> In model reviews.ReviewRequest: >>> Field 'description_rich_text' has been added >>> Field 'testing_done_rich_text' has been added >>> In model reviews.Review: >>> Field 'body_top_rich_text' has been added >>> Field 'body_bottom_rich_text' has been added >>> In model reviews.ReviewRequestDraft: >>> Field 'description_rich_text' has been added >>> Field 'testing_done_rich_text' has been added >>> In model accounts.Profile: >>> Field 'default_use_rich_text' has been added >>> CommandError: Your models contain changes that Django Evolution cannot >>> resolve automatically. >>> >>> >>> I've trying running evolve -- --hint --execute, but that fails with the >>> following >>> >>> CommandError: Error applying evolution: (1060, "Duplicate column name >>> 'default_use_rich_text'") >>> >>> >>> >>> I've checked that I have the latest django_evolution installed for my >>> platform (0.7.4). This is running on a MySql database. >>> >>> It seems like the evolution is trying to add columns that already >>> exist. Maybe a version table didn't get incremented in the prior >>> evolution? Any hints on how I can troubleshoot this? >>> >>> >>> >>> -- > Supercharge your Review Board with Power Pack: > https://www.reviewboard.org/powerpack/ > Want us to host Review Board for you? Check out RBCommons: > https://rbcommons.com/ > Happy user? Let us know! https://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 reviewboard+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- Supercharge your Review Board with Power Pack: https://www.reviewboard.org/powerpack/ Want us to host Review Board for you? Check out RBCommons: https://rbcommons.com/ Happy user? Let us know! https://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 reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Problems upgrading to 2.0.13 and 2.0.15
Any update here? On Friday, March 20, 2015 at 1:29:07 PM UTC-7, Daniel Dominguez wrote: > > Running --hint --evolve had not been done before. It was just my > experimenting after seeing this issue (with a current backup of the db > first of course). > > Anyhow, I've attached the sql dump you requested. > > Thanks! > > On Friday, March 20, 2015 at 8:28:36 AM UTC-7, Daniel Dominguez wrote: >> >> When I performed the upgrade form 2.0.12 to 2.0.13, the site-upgrade >> failed. It didn't seem to break our reviewboard instance, so I just >> ignored it at the time. I recently upgraded to 2.0.15, and the result is >> the same. Again, our reviewboard server seems to be fine, but this is >> starting to make me nervous. >> >> >> -- -- >> Creating tables ... >> 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: >> In model reviews.ReviewRequest: >> Field 'description_rich_text' has been added >> Field 'testing_done_rich_text' has been added >> In model reviews.Review: >> Field 'body_top_rich_text' has been added >> Field 'body_bottom_rich_text' has been added >> In model reviews.ReviewRequestDraft: >> Field 'description_rich_text' has been added >> Field 'testing_done_rich_text' has been added >> In model accounts.Profile: >> Field 'default_use_rich_text' has been added >> CommandError: Your models contain changes that Django Evolution cannot >> resolve automatically. >> >> >> I've trying running evolve -- --hint --execute, but that fails with the >> following >> >> CommandError: Error applying evolution: (1060, "Duplicate column name >> 'default_use_rich_text'") >> >> >> >> I've checked that I have the latest django_evolution installed for my >> platform (0.7.4). This is running on a MySql database. >> >> It seems like the evolution is trying to add columns that already exist. >> Maybe a version table didn't get incremented in the prior evolution? Any >> hints on how I can troubleshoot this? >> >> >> >> -- Supercharge your Review Board with Power Pack: https://www.reviewboard.org/powerpack/ Want us to host Review Board for you? Check out RBCommons: https://rbcommons.com/ Happy user? Let us know! https://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 reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Problems upgrading to 2.0.13 and 2.0.15
Running --hint --evolve had not been done before. It was just my experimenting after seeing this issue (with a current backup of the db first of course). Anyhow, I've attached the sql dump you requested. Thanks! On Friday, March 20, 2015 at 8:28:36 AM UTC-7, Daniel Dominguez wrote: > > When I performed the upgrade form 2.0.12 to 2.0.13, the site-upgrade > failed. It didn't seem to break our reviewboard instance, so I just > ignored it at the time. I recently upgraded to 2.0.15, and the result is > the same. Again, our reviewboard server seems to be fine, but this is > starting to make me nervous. > > > -- -- > Creating tables ... > 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: > In model reviews.ReviewRequest: > Field 'description_rich_text' has been added > Field 'testing_done_rich_text' has been added > In model reviews.Review: > Field 'body_top_rich_text' has been added > Field 'body_bottom_rich_text' has been added > In model reviews.ReviewRequestDraft: > Field 'description_rich_text' has been added > Field 'testing_done_rich_text' has been added > In model accounts.Profile: > Field 'default_use_rich_text' has been added > CommandError: Your models contain changes that Django Evolution cannot > resolve automatically. > > > I've trying running evolve -- --hint --execute, but that fails with the > following > > CommandError: Error applying evolution: (1060, "Duplicate column name > 'default_use_rich_text'") > > > > I've checked that I have the latest django_evolution installed for my > platform (0.7.4). This is running on a MySql database. > > It seems like the evolution is trying to add columns that already exist. > Maybe a version table didn't get incremented in the prior evolution? Any > hints on how I can troubleshoot this? > > > > -- Supercharge your Review Board with Power Pack: https://www.reviewboard.org/powerpack/ Want us to host Review Board for you? Check out RBCommons: https://rbcommons.com/ Happy user? Let us know! https://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 reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- MySQL dump 10.13 Distrib 5.5.41, for debian-linux-gnu (x86_64) -- -- Host: localhostDatabase: reviewboard -- -- -- Server version 5.5.41-0+wheezy1 /*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT */; /*!40101 SET @OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS */; /*!40101 SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION */; /*!40101 SET NAMES utf8 */; /*!40103 SET @OLD_TIME_ZONE=@@TIME_ZONE */; /*!40103 SET TIME_ZONE='+00:00' */; /*!40014 SET @OLD_UNIQUE_CHECKS=@@UNIQUE_CHECKS, UNIQUE_CHECKS=0 */; /*!40014 SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0 */; /*!40101 SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='NO_AUTO_VALUE_ON_ZERO' */; /*!40111 SET @OLD_SQL_NOTES=@@SQL_NOTES, SQL_NOTES=0 */; -- -- Table structure for table `django_evolution` -- DROP TABLE IF EXISTS `django_evolution`; /*!40101 SET @saved_cs_client = @@character_set_client */; /*!40101 SET character_set_client = utf8 */; CREATE TABLE `django_evolution` ( `id` int(11) NOT NULL AUTO_INCREMENT, `version_id` int(11) NOT NULL, `app_label` varchar(200) NOT NULL, `label` varchar(100) NOT NULL, PRIMARY KEY (`id`), KEY `django_evolution_f516c2b3` (`version_id`), CONSTRAINT `version_id_refs_id_946f97c5` FOREIGN KEY (`version_id`) REFERENCES `django_project_version` (`id`) ) ENGINE=InnoDB AUTO_INCREMENT=77 DEFAULT CHARSET=latin1; /*!40101 SET character_set_client = @saved_cs_client */; -- -- Dumping data for table `django_evolution` -- LOCK TABLES `django_evolution` WRITE; /*!4 ALTER TABLE `django_evolution` DISABLE KEYS */; INSERT INTO `django_evolution` VALUES (1,1,'auth','auth_delete_message'),(2,1,'auth','auth_unique_together_baseline'),(3,1,'contenttypes','contenttypes_unique_together_baseline'),(4,1,'sessions','session_expire_date_db_index'),(5,1,'accounts','is_private'),(6,1,'accounts','timezone'),(7,1,'accounts','open_an_issue'),(8,1,'accounts','extra_data'),(9,1,'accounts','timezone_length_30'),(10,1,'accounts','localsiteprofile_permissions'),(11,1,'accounts','unique_together_baseline'),(12,1,'accounts','profile_show_closed'),(13,1,'accounts','profile_should_send_email'),(14,1,'attachments','file_attachm
Re: Problems upgrading to 2.0.13 and 2.0.15
Hi Daniel, Running --hint --evolve is the quickest way to get into a mess with the signatures. If this was ever run in the past, it could have caused this. I've seen a similar issue recently, and know the fix for it, but I'll need you to send me an SQL dump with the contents of the django_evolution and django_project_version tables. (There's nothing confidential in them, as it's just records of database structure and when evolutions were performed.) Christian -- Christian Hammond - christ...@beanbaginc.com Review Board - https://www.reviewboard.org Beanbag, Inc. - https://www.beanbaginc.com -Original Message- From: Daniel Dominguez Reply: reviewboard@googlegroups.com > Date: March 20, 2015 at 8:28:40 AM To: reviewboard@googlegroups.com > Subject: Problems upgrading to 2.0.13 and 2.0.15 > When I performed the upgrade form 2.0.12 to 2.0.13, the site-upgrade > failed. It didn't seem to break our reviewboard instance, so I just > ignored it at the time. I recently upgraded to 2.0.15, and the result is > the same. Again, our reviewboard server seems to be fine, but this is > starting to make me nervous. > > > -- -- > Creating tables ... > 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: > In model reviews.ReviewRequest: > Field 'description_rich_text' has been added > Field 'testing_done_rich_text' has been added > In model reviews.Review: > Field 'body_top_rich_text' has been added > Field 'body_bottom_rich_text' has been added > In model reviews.ReviewRequestDraft: > Field 'description_rich_text' has been added > Field 'testing_done_rich_text' has been added > In model accounts.Profile: > Field 'default_use_rich_text' has been added > CommandError: Your models contain changes that Django Evolution cannot > resolve automatically. > > > I've trying running evolve -- --hint --execute, but that fails with the > following > > CommandError: Error applying evolution: (1060, "Duplicate column name > 'default_use_rich_text'") > > > > I've checked that I have the latest django_evolution installed for my > platform (0.7.4). This is running on a MySql database. > > It seems like the evolution is trying to add columns that already exist. > Maybe a version table didn't get incremented in the prior evolution? Any > hints on how I can troubleshoot this? > > > > -- > Supercharge your Review Board with Power Pack: > https://www.reviewboard.org/powerpack/ > Want us to host Review Board for you? Check out RBCommons: > https://rbcommons.com/ > Happy user? Let us know! https://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 reviewboard+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- Supercharge your Review Board with Power Pack: https://www.reviewboard.org/powerpack/ Want us to host Review Board for you? Check out RBCommons: https://rbcommons.com/ Happy user? Let us know! https://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 reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
