Zope 2.10.11 is missing lib/python/Zope2/version.txt

[David Glick]

This is causing getZopeVersion() in App.version_txt to report an unreleased version of Zope.

[Tres Seaver (tseaver)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

David Glick wrote:
> Public bug reported:
>
> This is causing getZopeVersion() in App.version_txt to report an
> unreleased version of Zope.
>
> ** Affects: zope2
> Importance: Undecided
> Status: New
>

 assigned tseaver

This is my bad, likely: I didn't RTFM Andreas wrote on releasing
"legacy" Zope versions.

Tres.
- --
===================================================================
Tres Seaver [phone] <email address hidden>
Palladion Software "Excellence by Design" http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAktYg9sACgkQ+gerLs4ltQ6CDwCfYwlh66//v9NCpqYpu9oHAJKF
qVsAoLh9/yqx40TbmM0Y5YxAGF+4YGBM
=sQD7
-----END PGP SIGNATURE-----

[Wolfgang Thomas (thomasw-syslab)]

For Plone users who have recently upgraded to 3.3.4 and now stumble across this error, here's a work-around that did the trick for me:

In the buildout.cfg, add (and use in "parts=") a new section:

[zope-versiontxt]
recipe = plone.recipe.command
command =
    touch ${buildout:directory}/parts/zope2/lib/python/Zope2/version.txt
    echo "Zope 2.10.11-final" > ${buildout:directory}/parts/zope2/lib/python/Zope2/version.txt

[Tres Seaver (tseaver)]

The "correct" workaround here is the run 'make version_txt' from within the Zope2 tree, which happens automatically whenever 'make install' is run. I suggest that the plone.recipe.zope2install egg be updated to run 'make version_txt'.

[Hanno Schlichting (hannosch)]

There won't be any new releases of Zope 2.10 (except for critical security issues), a workaround in plone.recipe.zope2install seems like the only way to go here.