Trac upgrade fails

[Johannes Spohr <johannes.spohr@…>]

After updating Bitten master to [729], the required Trac upgrade failed with a SQL error:

Adds a unique index on (config, platform, rev) to the bitten_build
table. Also drops the old index on bitten_build that serves no real
purpose anymore.
Traceback (most recent call last):
  File "/usr/bin/trac-admin", line 8, in <module>
    load_entry_point('Trac==0.11', 'console_scripts', 'trac-admin')()
  File "/usr/lib/python2.5/site-packages/Trac-0.11-py2.5.egg/trac/admin/console.py", line 1249, in run
    return admin.onecmd(command)
  File "/usr/lib/python2.5/site-packages/Trac-0.11-py2.5.egg/trac/admin/console.py", line 104, in onecmd
    rv = cmd.Cmd.onecmd(self, line) or 0
  File "/usr/lib/python2.5/cmd.py", line 219, in onecmd
    return func(arg)
  File "/usr/lib/python2.5/site-packages/Trac-0.11-py2.5.egg/trac/admin/console.py", line 1108, in do_upgrade
    self.__env.upgrade(backup=do_backup)
  File "/usr/lib/python2.5/site-packages/Trac-0.11-py2.5.egg/trac/env.py", line 442, in upgrade
    participant.upgrade_environment(db)
  File "/usr/lib/python2.5/site-packages/Bitten-0.6dev_r729-py2.5.egg/bitten/main.py", line 73, in upgrade_environment
    function(self.env, db)
  File "/usr/lib/python2.5/site-packages/Bitten-0.6dev_r729-py2.5.egg/bitten/upgrades.py", line 365, in add_config_platform_rev_index_to_build
    cursor.execute("CREATE UNIQUE INDEX bitten_build_config_rev_platform_idx ON bitten_build (config,rev,platform)")
  File "/usr/lib/python2.5/site-packages/Trac-0.11-py2.5.egg/trac/db/util.py", line 51, in execute
    return self.cursor.execute(sql)
  File "/usr/lib/python2.5/site-packages/Trac-0.11-py2.5.egg/trac/db/sqlite_backend.py", line 58, in execute
    args or [])
  File "/usr/lib/python2.5/site-packages/Trac-0.11-py2.5.egg/trac/db/sqlite_backend.py", line 50, in _rollback_on_error
    return function(self, *args, **kwargs)
sqlite3.IntegrityError: indexed columns are not unique

Maybe I could fix the database problem, but I'm not proficient enough in SQL to do that.

[osimons]

This is due to #214 - I'm closing this ticket and reopening the one we recently closed.