Good morning all,
after further testing we noticed our Zope2 virtualenv setup was done with the
ZMS3 (CMS) install routine using pip install ZMS3 --process-dependency-links.
This installed different package versions.
The original pip Zope2 uses these versions: http://pastebin.com/ZEwhVba0
The
thanks for the „shot“, yet disabling IPv6 locally on the VM does not help, same
error:
(server):
2015-05-06T10:05:51 INFO ZEO.StorageServer (127.0.0.1:44833) disconnected
--
2015-05-06T10:05:51 INFO ZEO.zrpc.Connection('S') (127.0.0.1:44835) received
handshake 'Z3101'
--
After more „research“ I see that the ZMS3 pip packages uses completely
different versions that don’t seem to be compatible with ZEO (at least Undo is
not working). I’m aware „undo“ is not a really used feature at all as revisions
most of the time are beeing implemented by products. My only fear
After further testing I was able to sort this one out by downgrading ZopeUndo
to 2.12.0 (pip install ZopeUndo==2.12.0 --force —upgrade).
PyPi only said 4.0 brought Py3 compability. Should I expect any problems using
ZopeUndo 2.12 + ZEO/ZODB4/ZODB3 with their latest versions?
Best, Sebastian
Hi Sebastian,
Am 06.05.2015 um 15:26 schrieb Sebastian Tänzer:
After further testing I was able to sort this one out by downgrading
ZopeUndo to 2.12.0 (pip install ZopeUndo==2.12.0 --force —upgrade).
PyPi only said 4.0 brought Py3 compability. Should I expect any
problems using ZopeUndo
This is the summary for test reports received on the
cmf-tests list between 2015-05-05 00:00:00 UTC and 2015-05-06 00:00:00 UTC:
See the footnotes for test reports of unsuccessful builds.
An up-to date view of the builders is also available in our
buildbot documentation:
CMF-trunk_Zope-trunk - Build # 732 - Successful:
Check console output at
https://jenkins.starzel.de/job/CMF-trunk_Zope-trunk/732/ to view the results.___
Zope-CMF maillist - Zope-CMF@zope.org
https://mail.zope.org/mailman/listinfo/zope-cmf
See
