Bug#613586: Still seems to be a problem with upgrades
On Mon, 21 Feb 2011 21:51:42 +0100, Vincent Bernat wrote: Got there after applying the dbconfig backup after a previously failed upgrade. I think that dbconfig-common made a backup of your database while it was partially upgraded. Unfortunately, those backups are not versioned. I don't find any previous version that exhibits a changed column before 0.5-1. Hi Mark! Another possibility is : 1. You upgraded from 0.3.1-6 to 0.5-1. 2. dbconfig-common make a backup of the database 3. An error occurred on database upgrade because of already existing indexes 4. You abort the upgrade 5. You try again to upgrade (to 0.5-1 or some newer version) 6. dbconfig-common overwrites the backup of the database with the half-upgraded database Does this scenario seems plausible to you? Thanks. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#613586: Still seems to be a problem with upgrades
It's posible that I tried retry on the first failure which as you say may have overwritten the backup. Having said that, on 0.3.1-6 grep changed /usr/share/dbconfig-common/data/roundcube/install/mysql shows `changed` datetime NOT NULL DEFAULT '1000-01-01 00:00:00', INDEX `changed_index` (`changed`) `changed` datetime NOT NULL DEFAULT '1000-01-01 00:00:00', So the 0.3.1-6 schema does contain 'changed' columns. Mark. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#613586: Still seems to be a problem with upgrades
On Wed, 23 Feb 2011 09:17:44 +, Mark Syms wrote: Having said that, on 0.3.1-6 grep changed /usr/share/dbconfig-common/data/roundcube/install/mysql shows `changed` datetime NOT NULL DEFAULT '1000-01-01 00:00:00', INDEX `changed_index` (`changed`) `changed` datetime NOT NULL DEFAULT '1000-01-01 00:00:00', So the 0.3.1-6 schema does contain 'changed' columns. Yes, but not for the identities table. First is for session table. Last is for contacts table. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#613586: Still seems to be a problem with upgrades
Having repaired my 0.3.1-6 database by comparing to the install script the upgrade does now complete. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#613586: Still seems to be a problem with upgrades
Using 0.5.1+dfsg-3 I get the following error. creating database backup in /var/cache/dbconfig-common/backups/roundcube_0.3.1-6.mysql. applying upgrade sql for 0.3.1-6 - 0.5-1. error encountered processing /usr/share/dbconfig-common/data/roundcube/upgrade/mysql/0.5-1: mysql said: ERROR 1060 (42S21) at line 49: Duplicate column name 'changed' -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#613586: Still seems to be a problem with upgrades
On Mon, 21 Feb 2011 13:25:02 +, Mark Syms m...@marksyms.me.uk wrote: Using 0.5.1+dfsg-3 I get the following error. creating database backup in /var/cache/dbconfig-common/backups/roundcube_0.3.1-6.mysql. applying upgrade sql for 0.3.1-6 - 0.5-1. error encountered processing /usr/share/dbconfig-common/data/roundcube/upgrade/mysql/0.5-1: mysql said: ERROR 1060 (42S21) at line 49: Duplicate column name 'changed' How did you get there? For example, if you downgraded your installation of 0.5.XX to 0.3.1-6 then upgraded again, this is normal. There is no downgrade procedure using dbconfig-common and the message you get cannot be avoided. If you aborted the installation of 0.5.XXX, then this is also normal that you get this message. If you downgraded, then restore a backup of the database and then upgrade again, this is a problem. For your specific case, if you just ignore the message, the postinst script will force the application of the whole upgrade file and your database will be fully upgraded. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#613586: Still seems to be a problem with upgrades
Got there after applying the dbconfig backup after a previously failed upgrade. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#613586: Still seems to be a problem with upgrades
OoO Vers la fin de l'après-midi du lundi 21 février 2011, vers 16:29, Mark Syms m...@marksyms.me.uk disait : Got there after applying the dbconfig backup after a previously failed upgrade. I think that dbconfig-common made a backup of your database while it was partially upgraded. Unfortunately, those backups are not versioned. I don't find any previous version that exhibits a changed column before 0.5-1. -- Don't just echo the code with comments - make every comment count. - The Elements of Programming Style (Kernighan Plauger) pgpvHX4bH9BSB.pgp Description: PGP signature
