This issue should hopefully be fixed upstream in 4.3.0.  There will be
no fix for 4.2.

                                        Juliusz



Reply via email to