you encounter the same error with version 2.2?
2.1.1 is done, and your problem should be gone.
2.1.1 should fix this problem in your environment. at the rate i’m going, that’ll be lunchtime.
try upgrading to 2.0.1, which should be available momentarily.