Hi,
I tried upgrading from 0.11.7 to 0.12, but after "trac-admin . upgrade"
I see these two errors:
Warning: Can't synchronize with the repository (Missing
"youngest_rev" in cache metadata). Look in the Trac log for more
information.
Trac detected an internal error: ValueError: year is out of range
This is on Centos5. Trac's report of system info is appended below.
Switching to a backup of the database prior to "trac-admin . upgrade"
makes both problems go away, even without reverting to 0.11.7, which I
have not yet done. (Of course I assume it's inadvisable to run a 0.11.7
database under 0.12 even when things do seem to work.)
Does anyone know what conditions can cause these symptoms, or how to fix
the problem?
The fact that the 0.11.7 database doesn't make 0.12 complain leads me to
ask, is seeing the "0.12" at the bottom of one's Trac pages a sufficient
indication of having successfully made the full step from 0.11.7 to
0.12? trac-admin reports 0.12, but since I used "python setup.py
install" rather than yum, I wonder if somehow 0.11.7 (or parts of it)
somehow remain and are serving the pages. Advice on what to check is
most welcome.
Thanks!
Don Sawtelle
[email protected]
System Information:
Trac:
0.12
Python:
2.4.3 (#1, Sep 3 2009, 15:37:37) [GCC 4.1.2 20080704 (Red Hat 4.1.2-46)]
setuptools:
0.6c8
SQLite:
3.3.6
pysqlite:
2.6.0
Genshi:
0.6
mod_python:
3.2.8
Pygments:
0.10
Subversion:
1.4.2 (r22196)
--
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.
