Hi David,
One thing I don't understand is why you have foreign PythonOption
definitions in your test setup. Are you sure you have re-created a
clean testconf.py file from testconf.py.in ? I've write a little bit
of documentation in test/README, please try to follow it.
It seems to me that the
Nicolas Lehuen wrote:
Hi David,
One thing I don't understand is why you have foreign PythonOption
definitions in your test setup. Are you sure you have re-created a
clean testconf.py file from testconf.py.in ? I've write a little bit
of documentation in test/README, please try to follow it.
Sébastien Arnaud wrote:
Hi,
I would like to report:
+1 Gentoo 2005.1 (amd64), Apache 2.0.55-prefork, Python 2.4.2
After replacing the troubling line (line 3038, configure):
from:
MP_VERSION=`echo $MP_VERSION | sed s/\\//g`
to (Deron's 1st suggestion):
MP_VERSION=`echo $MP_VERSION | sed
OK so my core group vote is +1 for this release.
It has been tested on a wide array of OSes, both threaded and forked
MPMs, Python 2.2, 2.3 and 2.4, so I guess it's okay. A threaded test
on MacOSX and Solaris would have been great but maybe the recommended
MPM on those platform is the forked one,
On Tue, 7 Feb 2006, Jim Gallacher wrote:
I assumed we would have a separate thread for the core vote, but what the
heck. :)
+1 is my core vote.
+1 from me as well.
Grisha
Gregory (Grisha) Trubetskoy wrote:
On Tue, 7 Feb 2006, Jim Gallacher wrote:
I assumed we would have a separate thread for the core vote, but what
the heck. :)
+1 is my core vote.
+1 from me as well.
When the core group votes for a release candidate, is it a consensus
vote or a
On Feb 7, 2006, at 9:32 AM, Jim Gallacher wrote:
When the core group votes for a release candidate, is it a
consensus vote or a majority vote? To quote from the Apache voting
guidelines, An action item requiring consensus approval must
receive at least 3 binding +1 votes and no vetos. An
Nicolas Lehuen wrote ..
OK so my core group vote is +1 for this release.
It has been tested on a wide array of OSes, both threaded and forked
MPMs, Python 2.2, 2.3 and 2.4, so I guess it's okay. A threaded test
on MacOSX and Solaris would have been great but maybe the recommended
MPM on
On Sun, Feb 05, 2006 at 09:10:15PM -0500, Jim Gallacher wrote:
Mod_python 3.2.7 tarball is available for test. Here's hoping this will
be to final time we need your help testing before the official release.
3.2.7 adds a fix for the connection read issue that was causing problems
on
+1 Fedora Core 4, Linux 2.6.15, Apache 2.0.54, Python 2.4.1
Jim Gallacher wrote:
Mod_python 3.2.7 tarball is available for test. Here's hoping this will
be to final time we need your help testing before the official release.
3.2.7 adds a fix for the connection read issue that was causing
Hi,
I hate to be the first one to report an issue with 3.2.7 tarball...
It might be related to my lack of knowledge (just joined the dev list
a few days ago), but here it is:
It is failing during the configure process...
[EMAIL PROTECTED] ~/mod_python-3.2.7 $ ./configure --with-apxs=/usr/
Hi Graham,
I am using:
[EMAIL PROTECTED] ~/mod_python-3.2.7 $ bash --version
GNU bash, version 3.1.7(1)-release (x86_64-pc-linux-gnu)
Copyright (C) 2005 Free Software Foundation, Inc.
I will look at if I can find later the BASH bug you are referring to.
I had the feeling that it was not
A couple of thoughts on this issue.
According to the gentoo bug report quoted below, the problem in
configure.in is the double backslash escape sequence in the line:
MP_VERSION=`echo $MP_VERSION | sed s/\\//g`
Changing this to:
MP_VERSION=`echo $MP_VERSION | sed s/\//g`
fixes it for bash
On 2/6/06, Jim Gallacher [EMAIL PROTECTED] wrote:
A couple of thoughts on this issue.
According to the gentoo bug report quoted below, the problem in
configure.in is the double backslash escape sequence in the line:
MP_VERSION=`echo $MP_VERSION | sed s/\\//g`
Changing this to:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
+1 Ubuntu 5.10 Breezy (amd64), Apache 2.0.54-worker, Python 2.4.2
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFD5/mTv4zJ7LQ+i84RAofQAKCb4ptmhPQa5QKRV/2sga60Xz4oAACcDygf
IB8UDE0zlcUr+I16DWbQ09U=
=WrUY
-END PGP
Hi,
I would like to report:
+1 Gentoo 2005.1 (amd64), Apache 2.0.55-prefork, Python 2.4.2
After replacing the troubling line (line 3038, configure):
from:
MP_VERSION=`echo $MP_VERSION | sed s/\\//g`
to (Deron's 1st suggestion):
MP_VERSION=`echo $MP_VERSION | sed 's///g' `
I guess now it's up
Mod_python 3.2.7 tarball is available for test. Here's hoping this will
be to final time we need your help testing before the official release.
3.2.7 adds a fix for the connection read issue that was causing problems
on FreeBSD.
Here are the rules:
In order for a file to be officially
+1 Debian (sid), Apache 2.0.55-prefork, Python 2.3.5
+1 Debian (sarge), Apache 2.0.54-worker, Python 2.3.5
+1 Debian (sarge), Apache 2.0.54-prefork, Python 2.3.5
Jim
Jim Gallacher wrote:
Mod_python 3.2.7 tarball is available for test. Here's hoping this will
be to final time we need your help
18 matches
Mail list logo
