Comment 4 for bug 330606

Yep. The patch which introduced this warning has been upstreamed in a different form. It is probabally logical to revert our version of this fix and pull out the upstream version. Will check into it.