Hi Christian,
> It's supposed to work... what Trac revision number are you using, > exactly? (should be >= r5163) This is the revision I have. > If you were using an older revision, before the forced database schema > version upgrade, it could happen that when upgrading a running > environment (e.g. using the mod_python front end), both the 0.10.3 and > 0.10.4 code base were active at the same time, in different server > processes. This resulted in two different and incompatible repository > sync cache mechanisms being active at the same time, resulting in the > 0.10.4 based requests to be "stuck" on some old revision. I was previously running 0.9. > > The database version bump has been done in order to prevent this to happen. > > To fix your situation, make sure you have the latest 0.10.4dev code, > stop your server, do an upgrade, a resync (or, if that's very costly, > simply do at the SQL level a " update system set value = '' where name = > 'youngest_rev' "), and restart your server. I have gone through the process before, but just tried again. It's a bit odd I tried the upgrade (which should just do nothing) and .. [breakout]$ trac-admin /home/mikelmaron/trac_sites/mapufacture upgrade Command failed: Database newer than Trac version I checked the db, and database_version in the system table was set to 20. Something out of order here? I went ahead and did the resync anyway, and restart, and youngest_rev was already set to '', and still trac gets out of sync on a subsequent checkin. -Mikel Mikel --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
