The problem is fixed in current cvs, and this is the bits of it that apply to 0.9.3.1. Applying this to the package, or upgrading to 0.9.4 when it comes out would probably be a good idea.
The problem is fixed in current cvs, and this is the bits of it that apply to 0.9.3.1. Applying this to the package, or upgrading to 0.9.4 when it comes out would probably be a good idea.