[Libvirt-cim] libvirt-cim rpm for Fedora 9 versus recent provider repository

[Dan Smith]

GY> The processor id changed to domanin_name/proc, then does the
GY> libvirt-cim rpm for Fedora 9 will reflect this recent changes? If
GY> so, when is it time to replace? Also the same issues in terms of
GY> MB versus KB for memory.  I'm not sure if libvirt-cim rpm freezed,
GY> then how cimtest are represent?  Do we have to branch cimtest into
GY> two parts, one for libvirt-cim rpm, the other for recent provider
GY> changes?

This is a good point.  The Fedora 9 RPM has been unchanged for a while
now, so none of the changes that you mention are included.  I think
that the test development should proceed to track the libvirt-cim
development tree, but perhaps there is a way that we can map FAIL to
XFAIL for older versions of the provider.

Does anyone have a suggestion for a reasonable way we could do this?

-- 
Dan Smith
IBM Linux Technology Center
Open Hypervisor Team
email: danms at us.ibm.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 188 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/libvirt-cim/attachments/20080410/c8288a0c/attachment.sig>