How to handel spinning when i686 versions of packages don't make it into the updates repo?

[Mike McLean]

On 01/04/2010 11:32 AM, Jesse Keating wrote:
> Multilib set is dynamically determined each compose.  If the package
> itself changes in a way that no longer triggers the multilib algorithm,
> then it will fall out of being multilib.

Is there a mechanism to remove 'fallen' multilib packages? If not, 
couldn't there be update errors? For that matter, what if the lingering 
older multilib package contains a security flaw?

My apologies if this has been discussed to death elsewhere.