Is this an instance of the policy stated in the following message? No, it's an instance of karl failing to update everything properly at one time. It should be ok after last night's update makes it around.