On Mon, 2 Apr 2001, bakkedai wrote:
On Tuesday 03 April 2001 06:33, Chris McDonough wrote:
Hi all,
The problem experienced under the combination of 2.3.1 and ZEO had to do with a lack of parity between the last ZEO release and the new conflict detection and resolution code provided by FileStorage in 2.3.1.
In order to make 2.3.1 work with ZEO, you will need to upgrade to the latest ZEO release, 0.5.0, available from http://www.zope.org/Products/ZEO. This involves shutting down the ZEO clients and ZEO server, unpacking the new ZEO files into the directory occupied by the older ZEO files on both the clients and the server (after backing up, of course), and restarting the server and the clients.
i think in my search to use 2.3.1, i installed the latest ZEO (thru cvs), and still saw the same problem. i'll verify this again this thursday, since this is production site, and i'd be walking on thin ice if i were to test it again today ;)
We just fixed the ZEO problem this afternoon, so you need to update ZEO, either with a fresh CVS update, or by getting ZEO 0.5.0 from zope.org. Jim -- Jim Fulton mailto:jim@digicool.com Python Powered! Technical Director (888) 344-4332 http://www.python.org Digital Creations http://www.digicool.com http://www.zope.org Under US Code Title 47, Sec.227(b)(1)(C), Sec.227(a)(2)(B) This email address may not be added to any commercial mail list with out my permission. Violation of my privacy with advertising or SPAM will result in a suit for a MINIMUM of $500 damages/incident, $1500 for repeats.