This issue had been fixed by revision rev#68295.
Sorry for the inconvenience, this issue had been introduced by a last minute change just before the intermediate release.