This issue was fixed in the 1.1.1 upstream release. Our fix was more subtle than the attached patch, but resolves the issue correctly.
A new package from of the latest (1.1.2) upstream release would resolve this bug along with a number of others.
-r
This issue was fixed in the 1.1.1 upstream release. Our fix was more
subtle than the attached patch, but resolves the issue correctly.
A new package from of the latest (1.1.2) upstream release would resolve
this bug along with a number of others.
-r