Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1456849 - Build spice-gtk with opus support
Build spice-gtk with opus support
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: spice-gtk (Show other bugs)
7.4
Unspecified Unspecified
unspecified Severity unspecified
: rc
: ---
Assigned To: Jonathon Jongsma
SPICE QE bug list
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-05-30 09:38 EDT by David Jaša
Modified: 2018-04-10 04:51 EDT (History)
8 users (show)

See Also:
Fixed In Version: spice-gtk-0.34-1.el7
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1456832
Environment:
Last Closed: 2018-04-10 04:50:15 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:0672 None None None 2018-04-10 04:51 EDT

  None (edit)
Description David Jaša 2017-05-30 09:38:08 EDT
+++ This bug was initially created as a clone of Bug #1456832 +++

Description of problem:
current version of spice-gtk has opus support, opus is also included in RHEL 7, so we shoud (finally) support Opus

Version-Release number of selected component (if applicable):


How reproducible:
always

Steps to Reproduce:
1. rpm -qR spice-gtk3 | grep opus // or see if opus is in BuildRequires
2.
3.

Actual results:
no opus dependency

Expected results:
spice-gtk depends on opus

Additional info:
Comment 1 Victor Toso 2017-05-30 09:46:07 EDT
Sure, in 7.5
Comment 6 errata-xmlrpc 2018-04-10 04:50:15 EDT
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://access.redhat.com/errata/RHBA-2018:0672

Note You need to log in before you can comment on or make changes to this bug.