I'd be largely tempted to not break freeze for this, and recommend the update/bodhi route here. (I believe there are several other xulrunner-induced upgrade paths broken recently as well)

For posterity, xulrunner bumps should be made branch specific, e.g. instead of
Release: 1%{?dist} -> 2%{?dist}
do
Release: 1%{?dist} -> 1%{?dist}.1

I believe there are several other xulrunner-induced upgrade paths broken recently as well

• blam-1.8.5-9.fc10 > blam-1.8.5-6.fc11
• gecko-sharp2-0.13-7.fc10 > gecko-sharp2-0.13-2.fc11
• galeon-2.0.7-9.fc10 > galeon-2.0.7-7.fc11
• Miro-2.0.3-3.fc10 > Miro-2.0.3-1.fc11
• google-gadgets-0.10.5-5.fc10 > google-gadgets-0.10.5-4.fc11
• mugshot-1.2.2-8.fc10 > mugshot-1.2.2-3.fc11

And I've ask C.Aillon to use "rpmdev-bumpspec --rightmost", hope he will do.

After latest Xulrunner update, perl-Gtk2-MozEmbed-0.08-6.fc11.1 is tagged
So no more issue with this package.

+

So this can be closed?

Yes, I close it.