[Zope-dev] Windows Installers
Hey all, Seems like we are seeing a shortage of volunteers for building the Zope Installers for Windows. I haven't seen Tim Peters around for a while, and Chris Withers seems to have stepped down now. I've chatted with Alan Runyan and he agreed to dedicate a person for doing this in exchange of a little publicity. Quoting him: Our build system has become quite extensive over the past two years. I would love to build the Zope installers. I would also appreciate some attribution on the first graphic that is displayed. Basically at the bottom about 20% of the graphic would say: '[LOGO] windows installer courtesy of Enfold System' Another alternative would be to add the installer as build to the buildbot @ zope.org, then we would have 'nightly' installer builds and once a release was cut one could just take one of these installers and declare it official. Thoughts? -- Sidnei da Silva Enfold Systemshttp://enfoldsystems.com Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214 ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Windows Installers
[Sidnei da Silva] Seems like we are seeing a shortage of volunteers for building the Zope Installers for Windows. IOW, nothing has changed :-) I haven't seen Tim Peters around for a while, and Chris Withers seems to have stepped down now. I'm around, but don't pay particular attention to all the Zope releases. If someone needs a Windows installer, I'm usually willing to make one (but probably won't notice a need for one without being poked). I've chatted with Alan Runyan and he agreed to dedicate a person for doing this in exchange of a little publicity. Quoting him: Our build system has become quite extensive over the past two years. I would love to build the Zope installers. I would also appreciate some attribution on the first graphic that is displayed. Basically at the bottom about 20% of the graphic would say: '[LOGO] windows installer courtesy of Enfold System' Not sure on exactly what that means, but doubt anyone would object, provided he's also willing to volunteer the time to produce the graphic and wrestle with InnoSetup to get it displayed. Another alternative would be to add the installer as build to the buildbot @ zope.org, then we would have 'nightly' installer builds and once a release was cut one could just take one of these installers and declare it official. Thoughts? Building the installer is usually easy. The hour or so it takes to make a real Windows release is usually consumed by testing, including manual testing of running as a Windows service. Sometimes there are also Windows-specific problems running the tests from an installation tree that never showed up running from a checkout tree. Of course if nobody cares about testing a release, a nightly installer build would work fine ;-) ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Windows Installers
On Mon, Jul 31, 2006 at 02:44:03PM -0400, Tim Peters wrote: | I'm around, but don't pay particular attention to all the Zope | releases. If someone needs a Windows installer, I'm usually willing | to make one (but probably won't notice a need for one without being | poked). Oh, cool. So we need a 2.8.8 and 2.9.4 installers. Note 2.9.4 changed the build procedure to be the same as 2.8.x again. I've made the changes, and hopefully it should work just fine. | I've chatted with Alan Runyan and he agreed to dedicate a person for | doing this in exchange of a little publicity. Quoting him: | | | Our build system has become quite extensive over the past two years. I | would love to build the Zope installers. I would also appreciate some | attribution on the first graphic that is displayed. Basically at the | bottom about 20% of the graphic would say: | '[LOGO] windows installer courtesy of Enfold System' | | | Not sure on exactly what that means, but doubt anyone would object, | provided he's also willing to volunteer the time to produce the | graphic and wrestle with InnoSetup to get it displayed. Since you are willing to handle the builds I won't bother for now. Next time you disappear :) -- Sidnei da Silva Enfold Systemshttp://enfoldsystems.com Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214 ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Windows Installers
[Sidnei da Silva[ So we need a 2.8.8 and 2.9.4 installers. OK, I uploaded a Windows installer for 2.8.8. There were two -all test failures: ERROR: test_OFS_ObjectManager__importObjectFromFile_xml (OFS.tests.test_XMLExportImport.XMLExportImportTests) -- Traceback (most recent call last): File C:\Code\Zope2.8\inst\build\lib\python\OFS\tests\test_XMLExportImport.py, line 102, in test_OFS_ObjectManager__i mportObjectFromFile_xml sub._importObjectFromFile(ostream.name, 0, 0) File C:\Code\Zope2.8\inst\build\lib\python\OFS\ObjectManager.py, line 592, in _importObjectFromFile ob=connection.importFile( File C:\Code\Zope2.8\inst\build\lib\python\ZODB\ExportImport.py, line 59, in importFile f = open(f, 'rb') IOError: [Errno 13] Permission denied: 'c:\\docume~1\\owner\\locals~1\\temp\\tmppr7uqt.xml' == ERROR: test_export_import_as_file_idempotent (OFS.tests.test_XMLExportImport.XMLExportImportTests) -- Traceback (most recent call last): File C:\Code\Zope2.8\inst\build\lib\python\OFS\tests\test_XMLExportImport.py, line 75, in test_export_import_as_file _idempotent newobj = importXML(connection, ostream.name) File C:\Code\Zope2.8\inst\build\lib\python\OFS\XMLExportImport.py, line 104, in importXML file=open(file) IOError: [Errno 13] Permission denied: 'c:\\docume~1\\owner\\locals~1\\temp\\tmpgj2cnm.xml' -- Ran 6229 tests in 1765.442s FAILED (errors=2) Note 2.9.4 changed the build procedure to be the same as 2.8.x again. I've made the changes, and hopefully it should work just fine. The 2.9.4 build started failing here: ... mkdir -p /cygdrive/c/Code/Zope2.9/inst/src cd /cygdrive/c/Code/Zope2.9/inst/src tar xzf ../tmp/Zope-2.9.4.tgz gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error exit delayed from previous errors make: *** [src/Zope-2.9.4/inst/configure.py] Error 2 I renamed the Zope 2.9.4 tarball download to worm around that, and then it failed here: mkdir -p /cygdrive/c/Code/Zope2.9/inst/src cd /cygdrive/c/Code/Zope2.9/inst/src tar xzf ../tmp/Zope-2.9.4.tgz touch src/Zope-2.9.4/inst/configure.py touch: cannot touch `src/Zope-2.9.4/inst/configure.py': No such file or directory make: *** [src/Zope-2.9.4/inst/configure.py] Error 1 Again it's fatally confused about whether the Zope tarball and/or unpacked directory root does or does not have -final in its name. I didn't repair this, I just wormed around it again (I have no idea what the /intent/ is now). Finally, the code for finding Inno Setup in common.mk was broken, trying to feed a native Windows path to the Cygwin bash shell. I replaced that on the tag (but not the branch) with similar (but working ;-)) code from the 2.8.8 build, essentially reverting this patch: http://svn.zope.org/Zope/branches/2.9/inst/WinBuilders/mk/common.mk?rev=69118r1=65837r2=69118 After that, everything worked fine, although the functional tests crapped out. ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
