The fix is in 0.1.19, not 0.1.18. It should be available shortly. Don't use --force-overwrite with it; there's no need.
(Sebastien, could you please include version numbers when you say that a bug is fixed, to prevent this kind of confusion?)
The fix is in 0.1.19, not 0.1.18. It should be available shortly. Don't use --force-overwrite with it; there's no need.
(Sebastien, could you please include version numbers when you say that a bug is fixed, to prevent this kind of confusion?)