This is tested and fixed in the 2.0 and 2.1 branches. You can download it now directly from those branches, or this fix will be in the 2.0.5 and 2.1.2 releases.
This is tested and fixed in the 2.0 and 2.1 branches. You can download it now directly from those branches, or this fix will be in the 2.0.5 and 2.1.2 releases.