Bug 1330571
Summary: | Add "gvir_domain_open_graphics_fd" patch | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Zeeshan Ali <zeenix> |
Component: | libvirt-glib | Assignee: | Libvirt Maintainers <libvirt-maint> |
Status: | CLOSED ERRATA | QA Contact: | Desktop QE <desktop-qa-list> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 7.3 | CC: | berrange, bgollahe, cfergeau, dyuan, jkoten, mclasen, mzhan, tpelka, vbenes |
Target Milestone: | rc | Keywords: | Rebase |
Target Release: | 7.3 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | libvirt-glib-0.2.3-1.el7 | Doc Type: | Rebase: Bug Fixes and Enhancements |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-11-04 04:43:34 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1043950 |
Description
Zeeshan Ali
2016-04-26 13:41:22 UTC
Cherry-picking APIs for backport in a versioned library is not something that should ever be done. Instead we should rebase the RPM to the version that contains the desired API, or even better, to the latest upstream release. Setting Rebase keyword to reflect comment 1. Zeeshan, what version do we need ? (In reply to Matthias Clasen from comment #3) > Setting Rebase keyword to reflect comment 1. Zeeshan, what version do we > need ? I think danpb wanted to just rebase to latest release, which would be v0.2.3. Yes, going forward, any time we rebase libvirt to latest upstream version, we're going to also aim to rebase libvirt-glib to the latest upstream version. So v0.2.3 is what we want to RHEL-7.3 at this time. Verified that other users can't approach other users VMs. gnome-boxes-3.14.3.1-10.el7 qemu-kvm-1.5.3-121.el7 libvirt-glib-0.2.3-1.el7 spice-gtk-0.31-5.el7 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. https://rhn.redhat.com/errata/RHBA-2016-2367.html |