Upgrading from 3.4 to 3.4.1
kaltheat at googlemail.com
Tue Dec 20 08:29:24 EST 2011
On Tue, 20 Dec 2011 00:39:49 +0100 Joe Marcus Clarke wrote:
>On 12/19/11 11:20 AM, kaltheat at googlemail.com wrote:
>> I wanted to update tinderbox, so I installed current version from ports and ran ./tc Upgrade as mentioned in the release notes. Doing this I got the following error:
>> INFO: Migrating database schema from 3.2.3 to 3.2.4 ...
>> /usr/local/bin/mysql: Unknown OS character set 'ISO8859-15'.
>> /usr/local/bin/mysql: Switching to the default character set 'latin1'.
>> ERROR 1050 (42S01) at line 1: Table 'build_groups' already exists
>> ERROR: Failed to load upgrade database schema.
>> ERROR: Database migration failed! Consult the output above for more
>> pkg_info shows this
>> tinderbox-3.4.1 Port build tinderbox system
>> I've two questions:
>> Do database schemes and tinderbox releases usually have different version numbers?
>Yes. We track a version number of the database called DSVERSION. This
>lets us do these incremental updates.
>> Can I ignore above error (maybe I missunderstood the meaning of upgrade and what I did was just an update)?
>This is not a good message. It seems like your schema may have been out
>of sync with the DSVERSION. As a workaround, if you go through the
>various .sql files in the upgrade directory, you can apply all of them
>in order until you get to DSVERSION 3.3. You will need to manually
>resolve conflicts like this one. When in doubt, drop the table, and
>reload it using the upgrade schema.
>> As far as I can see tinderbuilds work normal.
Thanks a lot! Worked fine so far. I applied every single SQL-statement manually. When there
were errors because an entity already exists, I checked if it had all attributes.
More information about the tinderbox-list