Re: [Zope-dev] Re: Zope 2.8 on hold
Hi, Am Samstag, den 07.05.2005, 12:56 -0400 schrieb Tim Peters: > Both appear to be due to that Zope 2.7.6 on Windows shipped with a > wrong (too old) version of pywin32, and continued to repackage pywin32 > in the old (certifiably insane <0.7 wink>) "flat" way. > > Mark Hammond submitted patches to install a correct version of > pywin32, and in a correct way. Those patches were incorporated into > WinBuilders, so it's hard to understand how Zope 2.7.6 on Windows got > built the way it did. Can only guess the installer was built using an > out-of-date WinBuilders checkout, with an out-of-date pywin32, applied > to an up-to-date Zope checkout. Yup. That's more than likely. I checked in *my* outdated version of the WinBuilders that did build in the Zope 2.7 and 2.8 branch 10 minutes ago. After that I read this thread catching up my email and noticed that they are outdated. :/ Anyway. Having them under the Zope trees should be better now, we just need to get to a working state again. Sorry for the inconvenience. Cheers, Christian -- gocept gmbh & co. kg - schalaunische str. 6 - 06366 koethen - germany www.gocept.com - [EMAIL PROTECTED] - phone +49 3496 30 99 112 - fax +49 3496 30 99 118 - zope and plone consulting and development signature.asc Description: This is a digitally signed message part ___ 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] Re: Zope 2.8 on hold
[Mark Hammond] > For me, WinBuilders *seemed* to work fine - until I realized that it was > reusing files from my previous 2.7 build. After nuking my 'build' > directory, I get this error: > > touch "/cygdrive/e/src/zope-packages/build/lib/python/Zope/Startup/run.py" > touch: creating > `/cygdrive/e/src/zope-packages/build/lib/python/Zope/Startup/run.py': No such > file or directory > make: *** > [/cygdrive/e/src/zope-packages/build/lib/python/Zope/Startup/run.py] Error 1 > > It appears the path should now be lib/python/Zope2/Startup/run.py. Yes, that was discussed here before. There are 3 instances of $(BUILD_DIR)/lib/python/Zope/Startup/run.py in the current WinBuilders HEAD zope.mk, and they all need s/Zope/Zope2/ to use WinBuilders for Zope trunk. Various version numbers are out of date too. For example, current HEAD zope.mk still says: ZOPEVERSION=2.7.5-final despite that 2.7.6 was released (and the released 2.7.6 final is broken on Windows: the shipped 2.7.6 contains your Windows service improvements, but still ships "the old" version of pywin32, and still in the broken "flat" way). Given those minor changes, WinBuilders worked fine for me applied to Zope trunk. > There was some talk about moving WinBuilders to under the main Zope > tree - that would solve a few problems related to the build - including > the "wrong pywin32 version one" (as it would have been much more > difficult to not update WinBuilders!) As above, that part got blown in Zope 2.7.6 anyway. I'll suggest that what the Windows Zope release process needs is someone to drive it who actually uses Zope on Windows <0.1 wink>. Play, pay, or forget it. > ... > Also, while I am here :) I mailed my CVS contributor form a couple of > weeks ago. What is the next step in the process? To whom did you mail it? I believe Jim (Fulton) handles those, so I'm copying him. Jim, did we get Mark's form? ___ 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] Re: Zope 2.8 on hold
> [Andreas Jung] > >>> At least the following are important (besides the problem with the > >>> Winbuilder) > > [Tim Peters] > >> What WinBuilders problem? I keep hearing there's "a > problem" there, > >> but don't know what it is -- and I had no problem using WinBuilders > >> for Zope 2.8. > > [Andreas] > > I know only that Christian had problems (according to his > > posting some days ago). I can not comment and can not value these > issues. But there seems to be something. For me, WinBuilders *seemed* to work fine - until I realized that it was reusing files from my previous 2.7 build. After nuking my 'build' directory, I get this error: touch "/cygdrive/e/src/zope-packages/build/lib/python/Zope/Startup/run.py" touch: creating `/cygdrive/e/src/zope-packages/build/lib/python/Zope/Startup/run.py': No such file or directory make: *** [/cygdrive/e/src/zope-packages/build/lib/python/Zope/Startup/run.py] Error 1 It appears the path should now be lib/python/Zope2/Startup/run.py. There was some talk about moving WinBuilders to under the main Zope tree - that would solve a few problems related to the build - including the "wrong pywin32 version one" (as it would have been much more difficult to not update WinBuilders!) Regarding the other bugs: Yuppie proposed 1776, but I'm afraid I don't understand the context of that report, so I'm unable to help. As Tim said, 1763 and 1711 don't apply. That leaves only 1728 and 1507, which appear the same issue - Yuppie just recently posted more information about that. Just before his mail I updated 1728 to indicate something similar, and that it is apparently not a "windows" bug. So I can't see anything else I can help with for 2.8. Also, while I am here :) I mailed my CVS contributor form a couple of weeks ago. What is the next step in the process? Cheers, Mark ___ 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] Re: Zope 2.8 on hold
[Andreas Jung] >>> At least the following are important (besides the problem with the >>> Winbuilder) [Tim Peters] >> What WinBuilders problem? I keep hearing there's "a problem" there, >> but don't know what it is -- and I had no problem using WinBuilders >> for Zope 2.8. [Andreas] > I know only that Christian had problems (according to his posting some > days ago). I can not comment and can not value these issues. But there > seems to be something. If you're talking about his posts to this list, those were all addressed some time ago, and all the problems in Zope 2.8's setup.py he was hitting have been repaired. If Christian still has problems, I haven't seen anything about them (neither on this list nor anywhere else). >> Note that these two aren't about Zope 2.8, they're about Zope 2.7.6: >> >> > http://www.zope.org/Collectors/Zope/1763 >> > http://www.zope.org/Collectors/Zope/1711 >> >> Both appear to be due to that Zope 2.7.6 on Windows shipped with a >> wrong (too old) version of pywin32, and continued to repackage pywin32 >> in the old (certifiably insane <0.7 wink>) "flat" way. >> >> Mark Hammond submitted patches to install a correct version of >> pywin32, and in a correct way. Those patches were incorporated into >> WinBuilders, so it's hard to understand how Zope 2.7.6 on Windows got >> built the way it did. Can only guess the installer was built using an >> out-of-date WinBuilders checkout, with an out-of-date pywin32, applied >> to an up-to-date Zope checkout. > Christian should know...as I said...I have no idea about how this > windows stuff works and what it does...so I depend on the competence of > you windows guys :-) It would help if Christian said something . I'm not sure the point of the above got across: the subject of this thread is "Zope 2.8 on hold", but the two issues identified above are not Zope 2.8 issues. They're Zope 2.7.6 issues. Zope 2.8 shouldn't have any problem with those. Zope-2.7.6-final-win32.exe from zope.org has those problems; they're not holding up 2.8. ___ 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] Re: Zope 2.8 on hold
--On Samstag, 7. Mai 2005 12:56 Uhr -0400 Tim Peters <[EMAIL PROTECTED]> wrote: [Andreas Jung] At least the following are important (besides the problem with the Winbuilder) What WinBuilders problem? I keep hearing there's "a problem" there, but don't know what it is -- and I had no problem using WinBuilders for Zope 2.8. I know only that Christian had problems (according to his posting some days ago). I can not comment and can not value these issues. But there seems to be something. Note that these two aren't about Zope 2.8, they're about Zope 2.7.6: http://www.zope.org/Collectors/Zope/1763 http://www.zope.org/Collectors/Zope/1711 Both appear to be due to that Zope 2.7.6 on Windows shipped with a wrong (too old) version of pywin32, and continued to repackage pywin32 in the old (certifiably insane <0.7 wink>) "flat" way. Mark Hammond submitted patches to install a correct version of pywin32, and in a correct way. Those patches were incorporated into WinBuilders, so it's hard to understand how Zope 2.7.6 on Windows got built the way it did. Can only guess the installer was built using an out-of-date WinBuilders checkout, with an out-of-date pywin32, applied to an up-to-date Zope checkout. Christian should know...as I said...I have no idea about how this windows stuff works and what it does...so I depend on the competence of you windows guys :-) -aj pgpauGqIyDdN0.pgp Description: PGP signature ___ 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] Re: Zope 2.8 on hold
[Andreas Jung] > At least the following are important (besides the problem with the > Winbuilder) What WinBuilders problem? I keep hearing there's "a problem" there, but don't know what it is -- and I had no problem using WinBuilders for Zope 2.8. Note that these two aren't about Zope 2.8, they're about Zope 2.7.6: > http://www.zope.org/Collectors/Zope/1763 > http://www.zope.org/Collectors/Zope/1711 Both appear to be due to that Zope 2.7.6 on Windows shipped with a wrong (too old) version of pywin32, and continued to repackage pywin32 in the old (certifiably insane <0.7 wink>) "flat" way. Mark Hammond submitted patches to install a correct version of pywin32, and in a correct way. Those patches were incorporated into WinBuilders, so it's hard to understand how Zope 2.7.6 on Windows got built the way it did. Can only guess the installer was built using an out-of-date WinBuilders checkout, with an out-of-date pywin32, applied to an up-to-date Zope checkout. ___ 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 )
