Matthew Gillen wrote: > Christian Boos wrote: >> Matthew Gillen wrote: >>> ... >>> "/usr/lib/python2.4/site-packages/trac/db/sqlite_backend.py", line 160, in >>> __init__\n timeout=timeout) >>> PythonHandler trac.web.modpython_frontend: SystemError: NULL result without >>> error in PyObject_Call >>> -------------------------------- >>> >>> >>>> So I don't see what's wrong with the 0.10.3.1 rpm now requiring >>>> python-sqlite2 (which seems to be pysqlite2 version 2.3.2). >>>> >>> Well, if it could read my sqlite3 databases, I wouldn't have a problem :-) >>> Incidentally, I tried doing a 'trac-admin <env> upgrade' to see if that >>> would >>> fix my db problems, but it did not. >>> >> This is a known issue, see http://initd.org/tracker/pysqlite/ticket/146. >> >> Unfortunately, this has only been fixed for 2.3.3, see the above ticket >> and the last comment for a (possible) workaround I've documented for 2.3.2. > > Ah, I see. Thanks Christian. I'll see about getting the python-sqlite2 > version updated to 2.3.3, since that seems to be the best solution.
Just an update for interested parties: The latest version of trac in FC6 extras (trac-0.10.3.1-2) does not have a dependency on python-sqlite2, so it is now safe to update. Thanks to Christian's excellent background information, I've filed a bug regarding getting python-sqlite2 updated to version 2.3.3. You can track the issue here if you're interested: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=231848 Matt --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~----------~----~----~----~------~----~------~--~---
