…for email is now implemented, so we can subvert BayeSpam as necessary 
It was simple enough, its more just the debugging to make it happen.
I have not had 3 problems in the last 2500 emails with BayeSpam being backed up by Apple Mail’s latent semantic analysis. They have been working well together. Alex is having a few more problems, and Amanda is getting nothing but spam even today, so a small balcklist for Viagra will make her happier
Popularity: 15%
Just a note for posterity: Subversion says to use SWIG 1.3.16, but the latest version was 1.3.19, so I tried to use that one. Big mistake 
SWIG 1.3.19 could not find the Python library, and therefore would not compile support for python, which Subversion needs to compile the python bindings. Anyway, I am now upgraded to SWIG 1.3.16, Python 2.2.3, and Subversion 0.24.2 to make it work.
Just had to vent…
Oh yeah, and don’t let me forget: Python cannot be built and installed as root. It must be built as a normal user, and then installed by root. Sheesh… It least it’s easy to use AFTER it is installed.
Popularity: 9%
Just upgraded to Tasks 1.6.1. Edited config.php and database.php, check the README, and it was good to go. This is also the test to make sure that I can blog from tasks to WordPress.
Alex, as an FYI, tasks has also been tested on Linux running Apache 2.0.45 and PHP 4.3.0
Popularity: 14%
San Mateo, CA - June 29, 2003 - For immediate release:
Today, the surprising hostile takover by Jaxen of SaxPath was announced and executed. The code formerly in the org.saxpath.* namespace will now live in the org.jaxen.saxpath.* namespace. Jaxen 1.1 beta2 will soon be released to include this functionality. If you are currently using SaxPath for something else and want to upgrade, you just need to change the package name, as everything else is the same. Users of Jaxen should not see any difference (excepting the namespace-based extension functions bug that was fixed). This was a pragmatic move for two reasons:
Scott Sanders was admitted as a new developer on the combined Jaxen/SaxPath codebase, and was in charge of the integration. Sanders was quoted as saying:
The move was very easy, and we are working to make it as painless as possible for everyone. IntelliJ did most of the work, I was just along for the ride.Code was committed, tests were re-run, everything looks great.
In other Jaxen news, a new HTMLXPath implementation was submitted to the jaxen mailing list, and after being very actively debugged for the last week, will be included in the Jaxen distribution, along with the existing DOM, dom4j, and jdom implementations.
Please email me or drop a comment here if you are using SaxPath without Jaxen.
Popularity: 10%
