This bug is still present on fully updated 6.06.2 releases.
I am attaching a custom package that installs cleanly on an updated 6.06.2 release, as the target package hasn't had any updated since the time this was first reported.
This bug is still present on fully updated 6.06.2 releases.
I am attaching a custom package that installs cleanly on an updated 6.06.2 release, as the target package hasn't had any updated since the time this was first reported.