Siddharth,
what should the (variant x rpm) mapping look like?

RPMs:
spice-gtk-devel-0.6-2.el6.i686.rpm
spice-glib-0.6-2.el6.i686.rpm
spice-gtk-python-0.6-2.el6.i686.rpm
spice-glib-devel-0.6-2.el6.i686.rpm
spice-gtk-0.6-2.el6.i686.rpm
spice-gtk-tools-0.6-2.el6.i686.rpm
spice-gtk-python-0.6-2.el6.x86_64.rpm
spice-glib-0.6-2.el6.x86_64.rpm
spice-gtk-0.6-2.el6.x86_64.rpm
spice-gtk-devel-0.6-2.el6.x86_64.rpm
spice-gtk-tools-0.6-2.el6.x86_64.rpm
spice-glib-devel-0.6-2.el6.x86_64.rpm

Adding devel_ack+ just in case, but I hope that's not really needed...

Wouldn't this just be pulled in by virt-manager as a dependency?

Yes, getting it as a dependency of virt-manager (or virt-viewer) will be the main use case. A few people may prefer to use spicy from spice-gtk-tools but that will be the exception rather than the norm

The latest virt-manager does depend on spice-gtk.  Moving this to MODIFIED since no other rel-eng action is needed.

# rpm -qpR virt-manager-0.9.0-5.el6.x86_64.rpm | grep spice
spice-gtk-python  

and spice-gtk-0.6-2 is present in the 0822.n.0 trees.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHEA-2011-1743.html