I think this bug is fixed in the upstream repo (commit e823140847cff74fe97c0a95c727d1a0fe883750). Is there any chance this could be fixed in time for precise?
I think this bug is fixed in the upstream repo (commit e823140847cff74 fe97c0a95c727d1 a0fe883750) . Is there any chance this could be fixed in time for precise?