We may have postponed the 5.0.3 release, but customers running 5.0.x who have this problem still need a patched package. Now that 6.0 is out, please backport this fix.
We may have postponed the 5.0.3 release, but customers running 5.0.x who have this problem still need a patched package. Now that 6.0 is out, please backport this fix.