Lowell Gilbert wrote:
Looks kind of like a problem that was fixed within the last few
days when the port was updated to the next release candidate.
Try updating your ports?
Looks kinda not.
I've got 2.0.3rc3 and I have the same problem.
I reported it several months ago and all I got to be told was that it's
a strange problem.
firstname.lastname@example.org mailing list
To unsubscribe, send any mail to "[EMAIL PROTECTED]"