Created attachment 340445 [details]
anki data file which triggers the problem

Description of problem:
Anki, a education program, stores its information in sqlite databases.
The newest version of anki tries to update the databases. E.g. columns are added and then it calls "vacuum". Usually with legacy_file_format set to off. This should regenerate the database files according to the new layout.

I'm getting this backtrace when doing this operation:

  File "/usr/lib/python2.5/site-packages/anki/deck.py", line 2479, in Deck
    deck = DeckStorage._upgradeDeck(deck, path)
  File "/usr/lib/python2.5/site-packages/anki/deck.py", line 2960, in _upgradeDeck
    deck.s.execute("vacuum")
  File "/usr/lib/python2.5/site-packages/anki/db.py", line 68, in execute
    x = self._session.execute(*a, **ka)
  File "/usr/lib/python2.5/site-packages/sqlalchemy/orm/session.py", line 628, in execute
    return self.__connection(engine, close_with_result=True).execute(clause, params or {})
  File "/usr/lib/python2.5/site-packages/sqlalchemy/engine/base.py", line 844, in execute
    return Connection.executors[c](self, object, multiparams, params)
  File "/usr/lib/python2.5/site-packages/sqlalchemy/engine/base.py", line 854, in _execute_text
    self.__execute_raw(context)
  File "/usr/lib/python2.5/site-packages/sqlalchemy/engine/base.py", line 916, in __execute_raw
    self._cursor_execute(context.cursor, context.statement, context.parameters[0], context=context)
  File "/usr/lib/python2.5/site-packages/sqlalchemy/engine/base.py", line 961, in _cursor_execute
    self._handle_dbapi_exception(e, statement, parameters, cursor)
  File "/usr/lib/python2.5/site-packages/sqlalchemy/engine/base.py", line 943, in _handle_dbapi_exception
    raise exceptions.DBAPIError.instance(statement, parameters, e, connection_invalidated=is_disconnect)
DatabaseError: (DatabaseError) database disk image is malformed 'vacuum' {}

I've communicated this problem with anki's upstream maintainer, and he couldn't reproduce the problem on his side. We've compared the versions of the relevant components and it turns out that python-sqlite2-2.3.3 is causing the problem.

I've compiled python-sqlite2-2.3.5 and the problem went away.


Version-Release number of selected component (if applicable):
python-sqlite2.i386 1:2.3.3-3.fc9 (there is no F10 build)


How reproducible:
100% on my side

Steps to Reproduce:
1. install newest anki (0.9.9.7.4): "yum update --enablerepo updates-testing anki"
2. download the attached file test.anki
3. start "anki /path/to/test.anki"
4. problem occurs (although there is no data loss)
5. kill the anki process, delete ~/.anki
6. download the attached file again (this is important, since anki has altered this file)
7. install python-sqlite2 scratch build from here: 
https://koji.fedoraproject.org/koji/taskinfo?taskID=1310129
8. start "anki /path/to/test.anki"
9. problem is gone ;-)

Actual results:
error message above

Expected results:
no error ;-)

Comments:
I know that the package is quite old, but it looks like that it is still in use by some other packages:
        python-sqlite2 is needed by (installed) synce-sync-engine-0.11.1-1.fc10.noarch
        python-sqlite2 is needed by (installed) nmap-frontend-2:4.68-3.fc10.i386
        python-sqlite2 is needed by (installed) PackageKit-0.3.15-2.fc10.i386
        python-sqlite2 is needed by (installed) gcompris-8.4.12-1.fc10.i386
Since rebuilding version 2.3.5 was really no problem, I hope that we can do this for F10 (and later as an update for F11).