i dont want to make a new installation on our live server, so i make a ugly
patch for our programmers that think that is a dev version because of the
'unreleased version' text.
i which zope version is the patched applied? 2.10.2?
Line 42 of /usr/lib/zope2.10/lib/python/App/version_txt.py
#
On 11/25/06, Christian Steinhauer <[EMAIL PROTECTED]> wrote:
As i see you fixed it. Can you give me a description how to fix it or have
you done a thread into an bugtracker?
http://svn.zope.org/Zope/branches/2.10/inst/Makefile.win.in?rev=71283&view=rev
--
Martijn Pieters
__
>Zope 2.9 and Zope 2.10 currently show up with "unreleased
>version" inside the control panel. App/version_txt.py tries
>to read the file lib/python/Zope2/version_txt. This file is
>usually created by the 'makefile'. The makefile of Zope 2.9
>create the file in the proper location however in
>>Hi,
>>
>>Zope 2.9 and Zope 2.10 currently show up with "unreleased
>>version" inside the control panel. App/version_txt.py tries
>>to read the file lib/python/Zope2/version_txt. This file is
>>usually created by the 'makefile'. The makefile of Zope 2.9
>>create the file in the proper locatio
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
Zope 2.9 and Zope 2.10 currently show up with "unreleased version" inside
the control panel. App/version_txt.py tries to read the file
lib/python/Zope2/version_txt. This file is usually created by
the 'makefile'. The makefile of Zope 2.9 create