This warning is way too scary for what it means, and the problem has
actually already been solved in the mvc branch, so let's not give our
users the heebie-jeebies.