trac-admin wiki upgrade fails

[Ron.Hauptfleisch.ctr@…]

OS:  Windows 2003 
Python Version:  ActiveState 2.5.1
DB: SQLite

C:\Documents and Settings\l.admin2>trac-admin C:\trac\IIMS wiki upgrade
Traceback (most recent call last):
  File "C:\Python25\Scripts\trac-admin-script.py", line 8, in <module>
    load_entry_point('Trac==0.11', 'console_scripts', 'trac-admin')()
  File "c:\python25\lib\site-packages\Trac-0.11-py2.5.egg\trac\admin\console.py"
, line 1249, in run
    return admin.onecmd(command)
  File "c:\python25\lib\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 "C:\Python25\lib\cmd.py", line 219, in onecmd
    return func(arg)
  File "c:\python25\lib\site-packages\Trac-0.11-py2.5.egg\trac\admin\console.py"
, line 697, in do_wiki
    create_only=['InterMapTxt'])
  File "c:\python25\lib\site-packages\Trac-0.11-py2.5.egg\trac\admin\console.py"
, line 779, in _do_wiki_load
    if self._do_wiki_import(filename, page, cursor, create_only):
  File "c:\python25\lib\site-packages\Trac-0.11-py2.5.egg\trac\admin\console.py"
, line 733, in _do_wiki_import
    old = list(rows)
  File "c:\python25\lib\site-packages\Trac-0.11-py2.5.egg\trac\admin\console.py"
, line 158, in db_query
    cursor.execute(sql, params)
  File "c:\python25\lib\site-packages\Trac-0.11-py2.5.egg\trac\db\util.py", line
 50, in execute
    return self.cursor.execute(sql_escape_percent(sql), args)
  File "c:\python25\lib\site-packages\Trac-0.11-py2.5.egg\trac\db\sqlite_backend
.py", line 58, in execute
    args or [])
  File "c:\python25\lib\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.OperationalError: Could not decode to UTF-8 column 'text' with text '= !
CamelCase =
New words created by smashing together capitalized words.

CamelCase is the original wiki convention for creating hyperlinks, with t

[Christian Boos]

“AlabamA” strikes again… (see CamelCase page, second paragraph).

The error is triggered while getting the text of the latest version already in the database, to check if an upgrade is needed.

So in this case, I've no idea how the content could have landed in SQLite database without having been properly encoded first. Maybe you did a major switch of the pysqlite version from 1.0 to 2.0? Maybe you did a dump/load sequence that somehow managed to modify the encoding?

Not sure what we can do here.

[Christian Boos]

Not sure what we can do here.

A .dump of the sqlite db in a file, fix the encoding if/where needed, followed by a .load.

Anyway, there's nothing we can do at the Trac level about this specific issue and no feedback providing additional details (like how we could reproduce the issue) was given, closing.