Hi there,
As you are running on r6009, I am hoping that this is not a side-
effect of change in 6006. As you say it 'always' does this, you are an
ideal candidate to help test this :-)
Could I ask you to:
1) open an editor and open your file at (sudo likely)
/usr/lib/python2.4/site-packages/Trac-0.11dev_r6009-py2.4.egg/trac/
env.py
2) At the bottom there is an open_environment() method, where there is
some comment about reloading a fresh environment on config changes.
Could you just comment out (#) the line that calls env.shutdown() and
save and close the file. Also, remove the compiled env.pyc if it
exists right next to env.py.
3) Restart your server and try editing the config again - do whatever
made your traceback appear.
:::simon
www.coderesort.com
On Sep 13, 8:41 am, "Joost Kraaijeveld" <[EMAIL PROTECTED]>
wrote:
> Hi,
>
> Whenever I edit the trac.ini with Gedit and refresh the current page to
> see the effects I get the following error of which I wonder if this is a
> bug or that it is by design :
>
> traceback (most recent call last):
> ...
> File
> "/usr/lib/python2.4/site-packages/Trac-0.11dev_r6009-py2.4.egg/trac/db/sqlite_backend.py",
> line 156, in __init__
> raise TracError('Database "%s" not found.' % path)
> TracError: Database "/var/lib/trac/testtrac/db/trac.db" not found.
>
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
