On Thu, Apr 10, 2008 at 08:59:27AM -0700, Dan Smith wrote:
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
Basically the Fedora-9 tree is frozen, but you should be able to push update for it after it has been released
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
Well you could push dated release to rawhide but it can get tiring quickly Daniel -- Red Hat Virtualization group http://redhat.com/virtualization/ Daniel Veillard | virtualization library http://libvirt.org/ veillard@redhat.com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/