File virtman-dont-specify-vte-version.patch of Package virt-manager

Overview Repositories Revisions Requests Users Attributes Meta

File virtman-dont-specify-vte-version.patch of Package virt-manager (Revision bc3e599f333576071fd080fac7e172ec)

Currently displaying revision bc3e599f333576071fd080fac7e172ec , Show latest

Creates a problem for gobject-introspection identifying what
version of vte is really allowed. Vte 2.91 is installed on the
host but the RPM is built requiring 2.90.

Index: virt-manager-3.0.0/virtManager/details/serialcon.py
===================================================================
--- virt-manager-3.0.0.orig/virtManager/details/serialcon.py
+++ virt-manager-3.0.0/virtManager/details/serialcon.py
@@ -12,12 +12,12 @@ from gi.repository import Gtk
 from virtinst import log
 
 # We can use either 2.91 or 2.90. This is just to silence runtime warnings
-try:
-    gi.require_version("Vte", "2.91")
-    log.debug("Using VTE API 2.91")
-except ValueError:  # pragma: no cover
-    gi.require_version("Vte", "2.90")
-    log.debug("Using VTE API 2.90")
+#try:
+#    gi.require_version("Vte", "2.91")
+#    log.debug("Using VTE API 2.91")
+#except ValueError:  # pragma: no cover
+#    gi.require_version("Vte", "2.90")
+#    log.debug("Using VTE API 2.90")
 from gi.repository import Vte
 
 import libvirt

Places

File virtman-dont-specify-vte-version.patch of Package virt-manager (Revision bc3e599f333576071fd080fac7e172ec)

Places