Comment 11 for bug 915618

(In reply to comment #4)

> I suspect this was a transient error caused selinux-policy changing
> incompatibly within the transaction (afaict selinux-policy has seen quite some
> changes recently), in which case there's not a whole lot that can be done about
> it with the currently available mechanisms: rpm loads the contexts at the
> beginning of transaction and if some of those contexts significantly change/go
> away, you'll see errors like this as rpm is trying to use the contexts that
> were defined when the transaction started. Or so the theory goes...

The specific error message may be transient, but I would call this a _design_ failure in BOTH rpm and selinux. Rpm has failed to preserve transaction integrity, and selinux is a willing accomplice. The only workaround is for rpm to require that no other modules may accompany selinux-* in the same transaction.