July 2006 - Zope-Dev

buildbot failure in Zope trunk 2.4 Windows 2000 zc-bbwin6
by buildbot＠zope.com 20 Jul '06

20 Jul '06

The Buildbot has detected a failed build of Zope trunk 2.4 Windows 2000 zc-bbwin6. Buildbot URL: http://buildbot.zope.org/ Build Reason: The web-page 'force build' button was pressed by '': Build Source Stamp: None Blamelist: BUILD FAILED: failed compile sincerely, -The Buildbot

1 0

Zope 2.9.4 broken ?
by dummy＠habmalnefrage.de 20 Jul '06

20 Jul '06

Hi, I've downloaded the latested tar ball fro Zope Zope-2.9.4-final.tgz, unpacked it and try to build/install it on SuSE Linux 9.2 with Python 2.4.3 /usr/src/packages/BUILD/Zope-2.9.4-final # ./configure Configuring Zope installation Testing for an acceptable Python interpreter... Python version 2.4.3 found at /usr/bin/python The optimum Python version (2.4.3) was found at /usr/bin/python. - Zope top-level binary directory will be /opt/Zope-2.9. - Makefile written. Next, run make. /usr/src/packages/BUILD/Zope-2.9.4-final # make "/usr/bin/python" "/usr/src/packages/BUILD/Zope-2.9.4-final/setup.py" \ build --build-base="/usr/src/packages/BUILD/Zope-2.9.4-final/build-base/python-2.4" --build-lib="/usr/src/packages/BUILD/Zope-2.9.4-final/build-base/python-2.4/build-lib" --build-scripts="/usr/src/packages/BUILD/Zope-2.9.4-final/build-base/python-2.4/build-scripts" --build-temp="/usr/src/packages/BUILD/Zope-2.9.4-final/build-base/python-2.4/build-temp" running build running build_py error: package directory 'build/lib/linux-i686-2/4/zope/app' does not exist make: *** [build] Error 1 Regards, Dirk -- "Feel free" – 10 GB Mailbox, 100 FreeSMS/Monat ... Jetzt GMX TopMail testen: http://www.gmx.net/de/go/topmail

2 1

buildbot failure in Zope trunk 2.4 Linux zc-buildbot
by buildbot＠zope.com 20 Jul '06

20 Jul '06

The Buildbot has detected a failed build of Zope trunk 2.4 Linux zc-buildbot. Buildbot URL: http://buildbot.zope.org/ Build Reason: changes Build Source Stamp: 6712 Blamelist: andreasjung,baijum,benji,benji_york,jens,jim,jinty,poster,srichter,tseaver BUILD FAILED: failed test sincerely, -The Buildbot

1 0

buildbot failure in Zope trunk 2.4 Windows 2000 zc-bbwin6
by buildbot＠zope.com 20 Jul '06

20 Jul '06

The Buildbot has detected a failed build of Zope trunk 2.4 Windows 2000 zc-bbwin6. Buildbot URL: http://buildbot.zope.org/ Build Reason: changes Build Source Stamp: 6712 Blamelist: andreasjung,baijum,benji,benji_york,jens,jim,jinty,poster,srichter,tseaver BUILD FAILED: failed compile sincerely, -The Buildbot

1 0

Zope 2.9.4
by Andreas Jung 19 Jul '06

19 Jul '06

If there are no objections, I plan to release Zope 2.9.4 in about one week (likely next Thu or Fri). Andreas

5 9

Re: [Zope-dev] 2.9.4? reStructuredText support?
by Richard Jones 19 Jul '06

19 Jul '06

On Sunday 09 July 2006 22:56, Jim Fulton wrote: > Whoever integrated reST didn't even read the documentation, much less > the code. FWIW. The ZReST product was originally released by me around 2002 - before those directives existed. According to the docutils HISTORY file, the directives themselves added in 2003. The *warning* about them was added in 2004. The configuration to *disable* them appears to have been added in 2005. What the hell docutils was doing turning this feature on by default... Richard

2 1

buildbot failure in Zope trunk 2.4 Linux zc-buildbot
by buildbot＠zope.com 17 Jul '06

17 Jul '06

The Buildbot has detected a failed build of Zope trunk 2.4 Linux zc-buildbot. Buildbot URL: http://buildbot.zope.org/ Build Reason: changes Build Source Stamp: 6657 Blamelist: adamg,alecm,andreasjung,dobe,fdrake,jim,poster,sidnei,tseaver BUILD FAILED: failed test sincerely, -The Buildbot

1 0

buildbot failure in Zope trunk 2.4 Windows 2000 zc-bbwin6
by buildbot＠zope.com 17 Jul '06

17 Jul '06

The Buildbot has detected a failed build of Zope trunk 2.4 Windows 2000 zc-bbwin6. Buildbot URL: http://buildbot.zope.org/ Build Reason: changes Build Source Stamp: 6657 Blamelist: adamg,alecm,andreasjung,dobe,fdrake,jim,poster,sidnei,tseaver BUILD FAILED: failed compile sincerely, -The Buildbot

1 0

port number for HTTPServer
by Miles Waller 17 Jul '06

17 Jul '06

Hi, I am trying to find out the port number for the HTTP service running in a zope instance. I tried using socket_map as used in the Control_Panel interface to report on running network services, but abandoned this because I need to get the same information when running in a debug instance as through the web. My next approach uses App.config.getConfiguration().servers to get the information fromn zope.conf directly. But a few things seem not quite right: - getConfiguration().servers gives me different lists through the debug prompt and through the web. why is this? - what is the most robust way to determine which of the listed servers is the HTTPServer? - is it ever possible that the servers list would contain more than one HTTPServer? The reason for doing this is so that zope can call out to an external program, and give it a notification url that the external program can call back on. Unfortunately I can't change this method of integration. Thanks for your help! Miles

2 1

Re: [Zope-dev] Re: Zope 2.9.4
by Tim Peters 16 Jul '06

16 Jul '06

[Tim] >> I used tags for ZODB until I gave in to complaints about that, and >> switched to using revision numbers. The real complaint about using a >> tagged external is that when the tag changes, SVN isn't smart enough >> to do an incremental update. Instead, when you update after an >> external tag changes: [Andreas] > What do you mean with "when the tag changes"? Not what I said: I said "[when] an /external/ tag" changes". I mean when you change an external tag _in_ project A _referencing_ the external tagged project B. Here A=Zope and B=ZODB, and the external tags in question are the ones referencing ZODB from within the svn:externals properties of various Zope directories. > A tag IMO should *never* change. The revision number associated with a tag within project B indeed shouldn't change. That's not what I'm talking about. I'm talking about how other projects reference project B: they have a choice of: 1. making their own copy of B 2. using svn:externals with a tag for B 3. using svn:externals with a revision number for B Read my msg again with that in mind, and it will make much more sense to you. I was describing the complaints about using choice #2. Zope Corp has tried all of those at various times. They all have different drawbacks, but the only one I found horribly unusable was #1 (because then N different projects have copies of B, and changes to copies of B's code get made from N different projects, and nobody bothers to merge those changes back into B itself -- people changing a copy of B from a different project often don't even _know_ they're changing "conceptually external" code; in effect, without absurd effort on the part of B's maintainer(s), the world ends up with B plus N forks of B). > ...

3 2