perl-embperl mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gerald Richter" <>
Subject RE: Debian Sarge und Embperl
Date Tue, 10 Aug 2004 04:27:48 GMT
> updates this to 17 August, 

That are good news! This gives us at least one additional weekend.

> but we really don't want to be 
> leaving it until the last day..

Yes, of course

> > Angus, are you able to make an upload before the 13 Aug. 
> when I give 
> > you a 2.0 on the 11 of August?
> Probably.  There isn't going to be any version of Embperl (2) 
> in sarge at all at the moment however, since the test suite 
> doesn't pass on alpha or ia64.
> See 
> for the logs of build failures and the details in the bug report at
> Gerald, if you can spend some time on it this week, I'm 
> pretty sure I can get you a login on an ia64 machine with 
> suitable debugging packages available.  I'll start the wheels 
> in motion for this now since it will take a day or so of 
> email-turnaround to arrange.

I have planned to spend some time this week and over the weekend. If you
could get such a login it would be great!

> Apparently I also have to deal with some changes in perl 5.8.[34]:

I think this error is already fixed in the current CVS version. The problem
is that newer Apache versions escape newlines in the error log, so the
number of lines make test get from the error log is 1 instead of 5, also the
content is the same.

I also will check Perl 5.8.4 today.

> Gerald, having looked at this I'm a little confused how the 
> error counter for error.htm *ever* counted the right number of errors.
> error.htm mostly produces perl warnings and 
> ignores errors matching /Warning/ ..

Yes, it only checks errors. That's because warnings are very different
between Perl versions and also errors have changed often, that's why this
function is so complicated. (and yes I know, make test is not an example for
well structured program, it's have been grown and grown and now it looks not
pretty nice)

> My apologies for not having chased the alpha/ia64 test 
> failures harder when we had more time to deal with it.

I have also didn't had much time to spend on it. Now, since we have a hard
limit, this should at least speed up 2.0 release :-)

Thanks for your help


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message