thanks for your fast replies, guys (of 2 weeks ago). unfortunately i finally had not time to do that, so i had to do my deployment without trac.
i would appreciate if you could please provide a link for solving that? i am also worried that if i upgrade trac and the database version i won't be able to access my projects unless i convert them. i don't want to sound "complainer" and lazy, but to gain widespread use of trac, i think this kind of issue should : * at the very least, warn about it clearlier (instead of the scary "file is encrypted" use something like "trying to access a trac database with a wrong db version. please check this and that or read here" * have a well documented (and easy to find) procedure on how to solve the issue, preferably pointed by the above suggested message 2007/10/3, Ulisses Reina Montenegro <[EMAIL PROTECTED]>: > Check out the versions of SQLite Python bindings in > both your laptop and production servers how to do that? 2007/10/3, Emmanuel Blot <[EMAIL PROTECTED]>: > > > Thanks in advance. > > Search for "database is encrypted" on trac.edgewall.org (you can > restrict the search to the wiki pages, this is a well-documented > 'issue' with SQLite v2 vs. v3 mismatch) > > HTH, > Manu > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to trac-users@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
