Please note that the bug described here was subsequently fixed.