Cole Robinson <crobinso@xxxxxxxxxx> writes: > So, plan for applying this. I want to get a new virt-manager release out > before mid February, and I'd like to hold off on applying these till after the > new release. Reason being is that a new enough libosinfo doesn't even exist > yet, so I want to give that some time to propagate, and at least exist in > fedora rawhide. And then we can have more time to try and take advantage of > the other libosinfo goodies for the follow up release. > > So let's claim virt-manager.git osdict.py as officially fossilized, no new > changes will be applied there. And if you can find out when the next libosinfo > release is, and possibly nudge it sooner rather than later, thatll help too. > Once the new virt-manager release goes out, and libosinfo is released, we can > apply these patches to git and go from there. > > Thoughts? that makes sense. We must depend from a future libosinfo release as the current version causes a crash whenever we try to get a full list of the OS and it misses some OS that are already part of osdict.py. I've pushed the series, rebased on top of master to the libosinfo-conversion branch. Giuseppe _______________________________________________ virt-tools-list mailing list virt-tools-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/virt-tools-list
