Comment 6 for bug 560145

Both should be fixed in the package uploads I did yesterday, so those error should resolve within the next couple of updates. I am marking this bug invalid since the original issue is now gone, though since we neither know why it happened nor how to prevent it, I would not dare talking about a fix :(