Re: [Phpwiki-talk] Nightly CVS stability HEADSUP

[Reini U. <ru...@x-...>]

John Cole schrieb:
> Reini,
>   Thanks for the warning.  Give a shout when you you want a round of testing
> again :-)
> 
>   Do you think it would be possible to tag the cvs tree occasionally when
> you think its at a semi-stable point?  Like last week when everything
> started working again :-)  I don't know how many people are subscribed to
> the checkin list, but I see every day how much work you put into this and a
> tag might provide good milestones for people to use.  I think last weeks cvs
> version is one of the best yet, it's been working very well in tests, so
> much so that I think I'm going to put it into production today.  

Good to hear, but I found a couple of more bugs today.
I believe that it works fine on normal setups, as it worked before on 
these platforms (apache1, windows+linux, dba+mysql), but Apache2 and 
php5 has issues I couldn't fix yet. php5 is coming close again.

I added a pages arg to dumphtml to finegrain it, and exclude will follow 
to exclude failing pages.
wikilens integration is that far that it doesn't fatal anymore (which is 
not yet the feature list we want...)

The updated pear DB and Cache libs seem to work fine, but I haven't yet 
fully tested them. Some workarounds are needed for old php's.

however, all pages dump now correctly and with a
$ html2ps *.html > FullDump.ps; ps2pdf FullDump.ps (...wait 5 min)
I get a fine 2MB compressed PDF of all pages.

subscribing to phpwiki-checkins is a good recommendation.


> -----Original Message-----
> From: php...@li...
> [mailto:php...@li...]On Behalf Of Reini
> Urban
> Sent: Sunday, June 20, 2004 1:35 PM
> To: php...@li...
> Subject: [Phpwiki-talk] Nightly CVS stability HEADSUP
> 
> 
> With all the latest php5, apache2, cgi and 
> allow_call_time_pass_reference fixes lately, I somehow broke the current 
> CVS code and I don't have to time to fix it properly today.
> So the nightly cvs version of today will be most likely broken.
> 
> php5 is broken for sure, somewhere in the list parser.
> apache2 is quite unstable.
> apache1 seems to work.
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/