Jens Vagelpohl wrote:
On 21 Dec 2005, at 18:47, Jim Fulton wrote:
I'll note, FWIW, that we don't do installs from Zope 3 checkouts.
I think it's worth asking whether this is an important requirement.
If it is, then we should make it work. Question is, is it worth
delaying the release? I don'
The Buildbot has detected a failed build of Zope trunk 2.4 Windows 2000
zc-bbwin.
Buildbot URL: http://buildbot.zope.org/
Build Reason: changes
Build Source Stamp: 2419
Blamelist: andreasjung
BUILD FAILED: failed test
sincerely,
-The Buildbot
___
Z
Chris Withers wrote:
Andreas Jung wrote:
I've never met ppl who actually used the HelpSys so that's why I am
raising the question about the value of the HelpSys. Lots of my
co-workers work with Zope on different levels (scripters, product
developers)...I've always pointed them to the Zope Bo
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: 2419
Blamelist: andreasjung
BUILD FAILED: failed test
sincerely,
-The Buildbot
___
Zope-D
--On 21. Dezember 2005 17:23:26 -0330 Rocky Burt <[EMAIL PROTECTED]>
wrote:
Personally I'd be a huge proponent of including SQLite in zope core. It
is extraordinarilly functional and has few requirements. I particularly
like using it to ensure unit tests against RDBMS connections work
pro
--On 21. Dezember 2005 18:07:49 + Chris Withers
<[EMAIL PROTECTED]> wrote:
How will Zope know when _not_ to add the content-type header?
Makes no sense to me. Either the application set the content-type header or
Zope does it for you. Check HTTPResponse.py.
How will Zope tell if th
On 12/21/05, Leonardo Rochael Almeida <[EMAIL PROTECTED]> wrote:
> My point is: I don't think there's anything wrong in the install
> procedure being different between the checkout and the tarball, but it
> should never take more than a couple of fixed (and documented) steps to
> convert a checkout
Jeff Kowalczyk wrote:
Andreas Jung wrote:
I'll raise the question again: what are the benefits of the HelpSys for
a Zope user?
I can't recall clicking on top frame of the ZMI or a 'Help!' link in the
past few years, either. Perhaps an equivalent or greater benefit would be
to rip out locally
Jens Vagelpohl wrote:
IMHO it is an important requirement. We're inviting a hailstorm of
questions and annoyed users by breaking this well-known routine for
checkouts.
I really think there is not a single good reason for having a different
experience for checkouts vs tarballs. It would e
Andreas Jung wrote:
The following usecase is not handled correctly by Zope:
When you call a PythonScript returning a Python unicode string then
the ZPublisher/HTTPResponse code will convert the unicode response
string using HTTPResponse.default_encoding to a Python string. The
default encoding
[Tim Peters]
>> ...
>> That was the problem. Turns out `bbwin` does have a compiler, but the
>> buildbot recipe didn't use it. After Jim fixed that, we have another
>> Windows-specific failure, in new code from ChrisM (this is on Zope
>> trunk, of course):
>>
>> Failure in test test_get_env
>> (Z
This has been my approach also. Not surprisingly, many of us worked on
these processes together and have 'sanitized them' over time. :) There
has always been 'another side' who either hasn't liked this procedure or
the 'make' voodoo and have come up with their own, or just haven't had
to do this
The Buildbot has detected a failed build of Zope trunk 2.4 Windows 2000
zc-bbwin.
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 failed slave lost
sincerely,
-The Buildbot
Hmmm... I *think* I just fixed this.
On Dec 21, 2005, at 3:48 PM, Tim Peters wrote:
[Tim Peters]
...
Failure in test test_checkPermission_proxy_roles_limit_access
(AccessControl.tests.testZopeSecurityPolicy.C_ZSPTests)
Traceback (most recent call last):
File "c:\python24\lib\unittest.py", l
Max M wrote:
> If there is another practical way to do it, that would be fine too. I
> don't know about sqllite. But if it's more difficulte than dropping a
> package into a directory it would be bad.
>
Personally I'd be a huge proponent of including SQLite in zope core. It
is extraordinarilly f
[Tim Peters]
> ...
> Failure in test test_checkPermission_proxy_roles_limit_access
> (AccessControl.tests.testZopeSecurityPolicy.C_ZSPTests)
> Traceback (most recent call last):
> File "c:\python24\lib\unittest.py", line 260, in run
> testMethod()
> File
> "C:\buildbot\.org\zc-bbwin--Windo
Just as a data point.
A lot of autoconf projects (the ones that made "./configure; make; make
install" famous) don't just run like that from a checkout, but they are
never more than 2 steps away from that.
The process for a checkout is usually more like
"./autoconf; ./automake; ./configure; make;
The Buildbot has detected a failed build of Zope trunk 2.4 Windows 2000
zc-bbwin.
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 test
sincerely,
-The Buildbot
_
--On 21. Dezember 2005 19:35:35 + Jens Vagelpohl <[EMAIL PROTECTED]>
wrote:
I really think there is not a single good reason for having a different
experience for checkouts vs tarballs. It would even lead to major
annoyance where I work right now, just to give a real life example. For
u
On 21 Dec 2005, at 18:47, Jim Fulton wrote:
I'll note, FWIW, that we don't do installs from Zope 3 checkouts.
I think it's worth asking whether this is an important requirement.
If it is, then we should make it work. Question is, is it worth
delaying the release? I don't know.
IMHO it is an
The Buildbot has detected a failed build of Zope trunk 2.4 Windows 2000
zc-bbwin.
Buildbot URL: http://buildbot.zope.org/
Build Reason: changes
Build Source Stamp: 2412
Blamelist: andreasjung
BUILD FAILED: failed test
sincerely,
-The Buildbot
___
Z
[Florent Guillaume]
> FYI test output is:
> ...
> 'zope[.]app[.])' is not recognized as an internal or external command,
> operable program or batch file.
> program finished with exit code 255
That was due to an ill-formed command line, which Jim repaired this
morning. Zope trunk and Zope 2.9 bra
I'd like to step back and see if we can agree on what is driving the desire
for "make install". I'll note that one reason is that it worked this way
before, but I don't think that that is a good enough reason to delay the
release.
I'll note one use case:
- A Zope deployer wants to deploy an un
Andrew Sawyers wrote:
On Wed, 2005-12-21 at 13:47 -0500, Jim Fulton wrote:
I'll note, FWIW, that we don't do installs from Zope 3 checkouts.
I think it's worth asking whether this is an important requirement.
If it is, then we should make it work. Question is, is it worth
delaying the release
On Wed, 2005-12-21 at 13:47 -0500, Jim Fulton wrote:
>
> I'll note, FWIW, that we don't do installs from Zope 3 checkouts.
> I think it's worth asking whether this is an important requirement.
> If it is, then we should make it work. Question is, is it worth
> delaying the release? I don't know
Martijn Faassen wrote:
Jens Vagelpohl wrote:
On 20 Dec 2005, at 08:51, Stefan H. Holek wrote:
On 18. Dez 2005, at 17:58, Tim Peters wrote:
Nobody should be installing from a checkout to begin with, right?
Ok, so that's probably where we disagree then ;-)
I almost exclusively work with
Jeff Kowalczyk wrote:
I didn't receive any feedback on zope-general, but it could just be a
problem with my environment that fails silently. Can anyone confirm that
this isn't pilot error before I file a bug? Thanks.
From the thread, it's not a pilot error, so could you please file a bug
if yo
Andreas Jung wrote:
I agree. I am also not happy with that. Unfortunately I have currently
no clue how to solve this issue (no idea about zpkg). WHat you can do is
the following:
- copy the checkout to the location where your software home should be
- run "configure; make inplace; make insta
Jens Vagelpohl wrote:
On 20 Dec 2005, at 08:51, Stefan H. Holek wrote:
On 18. Dez 2005, at 17:58, Tim Peters wrote:
Nobody should be installing from a checkout to begin with, right?
Ok, so that's probably where we disagree then ;-)
I almost exclusively work with checkouts, and I would thi
The Buildbot has detected a failed build of Zope trunk 2.4 Windows 2000
zc-bbwin.
Buildbot URL: http://buildbot.zope.org/
Build Reason: changes
Build Source Stamp: 2411
Blamelist: chrism
BUILD FAILED: failed test
sincerely,
-The Buildbot
___
Zope-D
The Buildbot has detected a failed build of Zope trunk 2.4 Windows 2000
zc-bbwin.
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 test
sincerely,
-The Buildbot
_
--On 21. Dezember 2005 17:10:19 +0100 Max M <[EMAIL PROTECTED]> wrote:
If there is another practical way to do it, that would be fine too. I
don't know about sqllite. But if it's more difficulte than dropping a
package into a directory it would be bad.
I mentioned to make it available as d
The Buildbot has detected a failed build of Zope branches 2.9 2.4 Windows 2000
zc-bbwin.
Buildbot URL: http://buildbot.zope.org/
Build Reason: The web-page 'force build' button was pressed by 'tim': try this
bbwin build by itself
Build Source Stamp: None
Blamelist:
BUILD FAILED: failed test
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: 2409
Blamelist: chrism
BUILD FAILED: failed test
sincerely,
-The Buildbot
___
Zope-Dev ma
On 21 Dec 2005, at 16:12, Jim Fulton wrote:
Jim Fulton wrote:
I'm going to go ahead with this update in hopes of resolving some
windows client problems that may be confounding our efforts to
run windows tests with buildbot.
Done
Great. I can see http://svn.zope.org works just fine.
With t
Jens Vagelpohl wrote:
Does that mean you're doing it? All necessary RPMs are on the box at /
root/svnupgrade/. Otherwise I can do it tomorrow morning (about 5 AM EST)
Yes, already done. They are also available in my home directory. :)
Jim
--
Jim Fulton mailto:[EMAIL PROTECTED]
Jim Fulton wrote:
I'm going to go ahead with this update in hopes of resolving some
windows client problems that may be confounding our efforts to
run windows tests with buildbot.
Done
Jim
--
Jim Fulton mailto:[EMAIL PROTECTED] Python Powered!
CTO (540) 361-17
Andreas Jung wrote:
Hi,
- Gadfly(DA) - do we really need this? We discussed this already. In my
opinion the purpose of Gadfly is only educational but nothing that one
really needs or uses for production. It could be removed and made
available for download on zope.org.
-1
From time to
Does that mean you're doing it? All necessary RPMs are on the box at /
root/svnupgrade/. Otherwise I can do it tomorrow morning (about 5 AM
EST)
jens
On 21 Dec 2005, at 16:08, Jim Fulton wrote:
I'm going to go ahead with this update in hopes of resolving some
windows client problems that m
I'm going to go ahead with this update in hopes of resolving some
windows client problems that may be confounding our efforts to
run windows tests with buildbot.
Jim
Jens Vagelpohl wrote:
On 19 Dec 2005, at 22:08, Jim Fulton wrote:
Sounds good. I'll announce that the repo will be down for m
The Buildbot has detected a failed build of Zope trunk 2.4 Windows 2000
zc-bbwin.
Buildbot URL: http://buildbot.zope.org/
Build Reason: changes
Build Source Stamp: 2402
Blamelist: andreasjung
BUILD FAILED: failed failed slave lost
sincerely,
-The Buildbot
The Buildbot has detected a failed build of Zope branches 2.9 2.4 Windows 2000
zc-bbwin.
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 failed slave lost
sincerely,
-The Bui
[EMAIL PROTECTED] wrote:
The Buildbot has detected a failed build of Zope branches 2.9 2.4 Windows 2000
zc-bbwin.
Buildbot URL: http://buildbot.zope.org/
Build Reason: changes
Build Source Stamp: 2398
Blamelist: efge,sidnei
BUILD FAILED: failed test
FYI test output is:
C:\WINDOWS\system32
The Buildbot has detected a failed build of Zope branches 2.9 2.4 Windows 2000
zc-bbwin.
Buildbot URL: http://buildbot.zope.org/
Build Reason: changes
Build Source Stamp: 2398
Blamelist: efge,sidnei
BUILD FAILED: failed test
sincerely,
-The Buildbot
__
The Buildbot has detected a failed build of Zope trunk 2.4 Windows 2000
zc-bbwin.
Buildbot URL: http://buildbot.zope.org/
Build Reason: changes
Build Source Stamp: 2397
Blamelist: efge,sidnei
BUILD FAILED: failed test
sincerely,
-The Buildbot
___
Z
The Buildbot has detected a failed build of Zope trunk 2.4 Windows 2000
zc-bbwin.
Buildbot URL: http://buildbot.zope.org/
Build Reason: changes
Build Source Stamp: 2391
Blamelist: andreasjung,anguenot,efge,sidnei
BUILD FAILED: failed test
sincerely,
-The Buildbot
Summary of messages to the zope-tests list.
Period Tue Dec 20 12:01:02 2005 UTC to Wed Dec 21 12:01:02 2005 UTC.
There were 8 messages: 8 from Zope Unit Tests.
Test failures
-
Subject: FAILED (errors=1) : Zope-2_7-branch Python-2.4.2 :
Linux
From: Zope Unit Tests
Date: Tue De
The Buildbot has detected a failed build of Zope branches 2.9 2.4 Windows 2000
zc-bbwin.
Buildbot URL: http://buildbot.zope.org/
Build Reason: changes
Build Source Stamp: 2390
Blamelist: andreasjung,anguenot,efge,sidnei
BUILD FAILED: failed test
sincerely,
-The Buildbot
_
Andreas Jung wrote:
- HelpSys - from a programmers view pretty much useless and not very
helpful. I consider to replace it with something more useful (not sure
we can re-use apidoc from Zope 3 in some way, perhaps the inclusion
of Dieter's Docfinder might be more useful for programmers)
49 matches
Mail list logo
