[ZCM] [ZC] 2210/ 6 Comment "Version string is 'unreleased version' instead of 'Zope 2.10.0-final'"

Issue #2210 Update (Comment) "Version string is 'unreleased version' instead of 'Zope 2.10.0-final'"
 Status Pending, Zope/bug low
To followup, visit:
  http://www.zope.org/Collectors/Zope/2210

==============================================================
= Comment - Entry #6 by Charlie_X on Nov 28, 2006 10:04 am

I just did a clean install and version.txt is missing from my Zope install
(/opt/Zope-2.10/lib/python/Zope-2)

Anything that depends upon getZopeVersion is going to choke.
________________________________________
= Comment - Entry #5 by ajung on Nov 22, 2006 3:04 pm

I fixed this on the Zope 2.10 by creating lib/python/Zope2/version.txt instead lib/python/version.txt.

I would like to see a 3rd-party confirmation if it really works.
________________________________________
= Comment - Entry #4 by ajung on Nov 21, 2006 12:34 pm

The 'instance' target of the makefile does not depend on the 'version_txt' target (as the target 'install' does). No idea if this is intentional or not.
________________________________________
= Comment - Entry #3 by ajung on Nov 21, 2006 12:31 pm

However this happens only when you create an instance in-place.
Not a big issue for me...
________________________________________
= Comment - Entry #2 by ajung on Nov 21, 2006 12:27 pm

This is also the case for 2.9.6 and 2.10.1. Looks as if "make instance" won't copy Zope2/version.txt since the file is present in the archive.
________________________________________
= Request - Entry #1 by smt on Oct 7, 2006 3:46 pm

The DebugInfo of my Zope 2.10.0 installation shows "unreleased version" instead of "Zope 2.10.0-final".

This is caused by a "version.txt" file in the Zope2 package folder. See line 34 of file "App/version_txt.py":
  fn = os.path.join(os.path.dirname(Zope2.__file__), 'version.txt')

==============================================================