Hi

I have a question that may be relatively simple to answer for someone with a
strong knowledge of trac's internal operation.

Interested in accessing some of the Trac 0.9 releases new features, I attempted
an upgrade trac systems in two very different environments from 0.8.4 to 0.9.x.

One, a production Solaris 9 (Sparc) environment hosting multiple projects with
ldap authentication (which I rolled back to 0.8.4 immediately after detecting
issues) that had been running flawlessly for about 6 months.

The other, a test system I have at home with Fedora Core 4 without fancy access
control also failed.

Given that the two upgrades failed with identical outcomes on very different
hardware and operating systems I feel something has been systematically
overlooked by me in both cases.

To perform the upgrade I also upgraded from sqlite 2.8.x to sqlite 3.2.8. The
sqlite3 upgrade and the pysqlite 2.0.5 upgrade to accompany it worked ok and the
python tests (python 2.3.5) worked 100%. I also upgraded clearsilver to 0.10.2
today with no degradation in performance on the 0.8.4 installation so I can't
see this being a problem. I did not upgrade the Subversion server and it still
stands at 1.2.3 for both environments.

I dumped the 0.8.4 database and migrated for 0.9.x using the commands in the
documentation for the upgrade. Tables seem completely normal when accessed using
 the sqlite3 console. I also added the PythonHandler text that is now required
for mod_python, disabling the older syntax.

As recommended, I renamed the /usr/local/share/trac cgi-bin,htdocs,templates
directories and the /usr/local/lib/python2.3/site-packages/trac directory

I installed static.cgi and the trac.cgi in the apache2 cgi-bin with user and
group as nobody as required by the servers.

I ran the upgrade and the wiki upgrade command.

I also ran the resync command as the first thing I noticed was the timeline had
gone crazy (lost).

The things I noticed that went wrong after the upgrade are:
- The banner image defined in trac.ini is no longer displayed on any page.
- The repository contents and the metadata on the repository are no longer
displayed correctly, all metadata on files is missing now.
- Attempting to edit wiki content now fails to be bring up the edit screen, the
 calling page remains in the browser
- Timeline has lost all its information and is not regenerated with resync
- There are probably other small things that I can't remember off the top of
my head.

I expect that I have either failed to remove an older file from the Trac 0.8.4
release, forgotten to copy a new file for one of the dependencies into a
relevant location, inadvertently introduced permissions problems or duplicate
libraries files that are conflicting, or maybe not inserted/removed something in
the configuration files needed when two pysqlite (1.x and 2.x) and sqlite (2.x
and 3.x) are installed concurrently attempting to use Trac 0.9.x. Maybe I have
overlooked a change that is important in the httpd.conf with this sort of
configuration?

It is strange the subversion relate functions have all had trouble pulling data
out with 0.9, do I need to recompile the bindings for python to subversion, I
wouldn't have thought so???

I would appreciate any suggestions on what may be the cause of this problem with
the upgrade as it appears to be 90% ok given data is pulled out and rendered
okay in the browser. To me this indicates clearsilver, pysql and sqlite3 are
working ok. I have not upgraded python for this new version of trac, it has
always been 2.3.5.

As I indicated if I roll back to the 0.8.4 configuration then all is okay.

Sure is a strange bunch of issues to appear at the same time, makes me think it
could be a misconfiguration issue I have introduced.

I tried 0.9.3 today and the outcome is the same.

Thanks & regards
Anthony
_______________________________________________
Trac mailing list
[email protected]
http://lists.edgewall.com/mailman/listinfo/trac

Reply via email to