Zope 2.8.0b2: WinBuilder issue
Howdy, The InnoSetup complained about pythonservice.exe to be missing during packaging the installer. Any ideas? Cheers, Christian -- gocept gmbh & co. kg - schalaunische str. 6 - 06366 koethen - germany www.gocept.com - ct@gocept.com - phone +49 3496 30 99 112 - fax +49 3496 30 99 118 - zope and plone consulting and development
Howdy,
The InnoSetup complained about pythonservice.exe to be missing during packaging the installer. Any ideas?
What path does the final Inno file refer to? Is the entire path missing, or just that file missing from that path? IIRC, we explode the pywin32 installer and grab the file from there. I'm pretty sure that file is in pywin32, but can't speculate why it fails to end up where Inno wants it. Mark
Morning, Am Donnerstag, den 26.05.2005, 09:03 +1000 schrieb Mark Hammond:
What path does the final Inno file refer to? Is the entire path missing, or just that file missing from that path? IIRC, we explode the pywin32 installer and grab the file from there. I'm pretty sure that file is in pywin32, but can't speculate why it fails to end up where Inno wants it.
It doesn't look like that file is around anywhere in the tmp,src or build directories: Administrator@zope /cygdrive/c/zope/build_28 $ find . -name "win*.exe" ./build/bin/Lib/site-packages/win32popenWin9x.exe ./src/Python-2.3.5/Lib/distutils/command/wininst.exe ./src/Python-2.3.5-extract/wininst.exe ./src/pywin32-204.win32-py2.3/PLATLIB/win32/win32popenWin9x.exe I'm running the whole thing again to check for possible earlier errors that eventually got hidden... Christian -- gocept gmbh & co. kg - schalaunische str. 6 - 06366 koethen - germany www.gocept.com - ct@gocept.com - phone +49 3496 30 99 112 - fax +49 3496 30 99 118 - zope and plone consulting and development
Am Donnerstag, den 26.05.2005, 09:03 +1000 schrieb Mark Hammond:
What path does the final Inno file refer to? Is the entire path missing, or just that file missing from that path? IIRC, we explode the pywin32 installer and grab the file from there. I'm pretty sure that file is in pywin32, but can't speculate why it fails to end up where Inno wants it.
It doesn't look like that file is around anywhere in the tmp,src or build directories:
Administrator@zope /cygdrive/c/zope/build_28 $ find . -name "win*.exe" ./build/bin/Lib/site-packages/win32popenWin9x.exe ./src/Python-2.3.5/Lib/distutils/command/wininst.exe ./src/Python-2.3.5-extract/wininst.exe ./src/pywin32-204.win32-py2.3/PLATLIB/win32/win32popenWin9x.exe
Your original mail said:
The InnoSetup complained about pythonservice.exe to be missing during packaging the installer. Any ideas?
PythonService.exe wont match "win*.exe" Mark
Am Donnerstag, den 26.05.2005, 16:54 +1000 schrieb Mark Hammond:
PythonService.exe wont match "win*.exe"
Yeah, right. Stupid computers ... ;) So this file of course exists, in a different path. Inno expected \build \bin\lib\site-packages\win32\PythonService.exe and it is in \build\bin \lib\site-packages\PythonService.exe Should I change Inno's reference (have to do that for the b2 release) or should it go into a different path in future? Additionally, it then asked for PyWinTypes23.dll which is in ./build/bin/Lib/site-packages/PyWinTypes23.dll instead of ./build/bin/Lib/site-packages/pywin32_system32/PyWinTypes23.dll. Looks like a couple of things are ending up in the wrong places ... Cheers, Christian -- gocept gmbh & co. kg - schalaunische str. 6 - 06366 koethen - germany www.gocept.com - ct@gocept.com - phone +49 3496 30 99 112 - fax +49 3496 30 99 118 - zope and plone consulting and development
So this file of course exists, in a different path. Inno expected \build \bin\lib\site-packages\win32\PythonService.exe and it is in \build\bin \lib\site-packages\PythonService.exe
Should I change Inno's reference (have to do that for the b2 release) or should it go into a different path in future?
Additionally, it then asked for PyWinTypes23.dll which is in ./build/bin/Lib/site-packages/PyWinTypes23.dll instead of ./build/bin/Lib/site-packages/pywin32_system32/PyWinTypes23.dll.
Looks like a couple of things are ending up in the wrong places ...
This sounds alot like a "win32all" package, not a pywin32 one. Looking inside the pywin32 one: % unzip -l pywin32-204.win32-py2.3.exe | grep pythonservice warning [pywin32-204.win32-py2.3.exe]: extra 63975 bytes at beginning or within zipfile (attempting to process anyway) 20480 04-12-05 18:11 PLATLIB/win32/pythonservice.exe % unzip -l pywin32-204.win32-py2.3.exe | grep 23.dll warning [pywin32-204.win32-py2.3.exe]: extra 63975 bytes at beginning or within zipfile (attempting to process anyway) 311296 04-12-05 18:09 PLATLIB/pywin32_system32/pythoncom23.dll 98304 04-12-05 18:08 PLATLIB/pywin32_system32/pywintypes23.dll ie, exactly where you say Inno wants them. Are you sure you are using pywin32-204.win32-py2.3.exe from sourceforge? Mark
participants (2)
-
Christian Theune -
Mark Hammond