I suggest that we use the workaround from comment #17 to create a specific package for Windows only, without committing it to the trunk, that we could use to release a fixed version very quickly (0.91.0.1?). The bug is too visible to be left unpatched IMHO.
I suggest that we use the workaround from comment #17 to create a specific package for Windows only, without committing it to the trunk, that we could use to release a fixed version very quickly (0.91.0.1?). The bug is too visible to be left unpatched IMHO.