Am 05.02.2006 um 23:48 schrieb Stephen Deasey:
On 2/4/06, Zoran Vasiljevic <[EMAIL PROTECTED]> wrote:
Hi!
I have uploaded the 4.99.1 release to SF.
nsd/nsd.h:114
#define NSD_TAG "$Name: $"
Don't forget to use the magic 'cvs export' when making a release:
AHA! That was the missing p
This should make the new aggressive cleanups unnecessary:
% make clean
...
/bin/rm -Rf *~ *.bak
...
Sorry, maybe make clean is way too aggressive regarding backup files
--
Vlad Seryakov
571 262-8608 office
[EMAIL PROTECTED]
http://www.crystalballinc.com/vlad/
On 2/4/06, Zoran Vasiljevic <[EMAIL PROTECTED]> wrote:
> Hi!
>
> I have uploaded the 4.99.1 release to SF.
nsd/nsd.h:114
#define NSD_TAG "$Name: $"
Don't forget to use the magic 'cvs export' when making a release:
http://sourceforge.net/mailarchive/message.php?msg_id=11432982
This should
Am 05.02.2006 um 09:59 schrieb Stephen Deasey:
Hmm, looks like Ns_CompressGzip() returns an error if zlib support is
not enabled. I guess we just issue a warning at configure time, and
come up with a workaround for the test.
In that case (if the warning is present) the test can workarround th
On 2/5/06, Zoran Vasiljevic <[EMAIL PROTECTED]> wrote:
>
> Am 05.02.2006 um 09:22 schrieb Stephen Deasey:
>
> > I think the build should fail if zlib is
> > not found.
>
> ...and if you configured with --without-zlib?
> Hm...
>
> The problem is, as I see that the test routines
> cannot check if th
Am 05.02.2006 um 09:22 schrieb Stephen Deasey:
I think the build should fail if zlib is
not found.
...and if you configured with --without-zlib?
Hm...
The problem is, as I see that the test routines
cannot check if the zlib is compiled-in or not.
I usually build with --without-zlib for some
On 2/5/06, Zoran Vasiljevic <[EMAIL PROTECTED]> wrote:
>
> Am 05.02.2006 um 07:38 schrieb Zoran Vasiljevic:
>
> > ns_info-2.19.1 basic operation FAILED
> > Contents of test case:
> >
> > expr {[llength [ns_info pools]]<=0}
> >
> > Result was:
> > 0
> > Result should have be
Am 05.02.2006 um 07:38 schrieb Zoran Vasiljevic:
ns_info-2.19.1 basic operation FAILED
Contents of test case:
expr {[llength [ns_info pools]]<=0}
Result was:
0
Result should have been (exact matching):
1
ns_info-2.19.1 FAILED
I think this test is broken. It ass
Am 05.02.2006 um 00:00 schrieb Vlad Seryakov:
Works fine for me, no failures
ns_info-2.19.1 basic operation FAILED
Contents of test case:
expr {[llength [ns_info pools]]<=0}
Result was:
0
Result should have been (exact matching):
1
ns_info-2.19.1 FAILED
I get o
Works fine for me, no failures
Stephen Deasey wrote:
On 2/4/06, Zoran Vasiljevic <[EMAIL PROTECTED]> wrote:
Hi!
I have uploaded the 4.99.1 release to SF.
I'm getting some test failures:
Tests began at Sat Feb 04 03:13:58 PM MST 2006
http.test
http_byteranges.test
http_chunked.test
[04/F
On 2/4/06, Zoran Vasiljevic <[EMAIL PROTECTED]> wrote:
> Hi!
>
> I have uploaded the 4.99.1 release to SF.
I'm getting some test failures:
Tests began at Sat Feb 04 03:13:58 PM MST 2006
http.test
http_byteranges.test
http_chunked.test
[04/Feb/2006:15:13:58][4858.1087490992][-conn:test:0] Notice
Hi,
> I have uploaded the 4.99.1 release to SF.
> Also, the modules are now part of the release.
great! I updated minor parts of the Wiki to reflect that.
> In the meantime, lets start adding the documentation.
> Ah, yes... at the point somebody is adding the documentation,
> he can immediately
Hi!
I have uploaded the 4.99.1 release to SF.
Also, the modules are now part of the release.
I will bump the versions now to 4.99.2 for
future interim releases. According to me, we
could/should get to the 5.0 when:
a. documentation is ready
b. new writer-thread support is finalized
The a.
13 matches
Mail list logo
