Bug 1310097 - Build spice-client-msi for RHEL 7 RHEV 4.0
Summary: Build spice-client-msi for RHEL 7 RHEV 4.0
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: rhevm-spice-client
Version: 4.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ovirt-4.0.0-beta
: ---
Assignee: Uri Lublin
QA Contact: SPICE QE bug list
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-19 12:47 UTC by Sandro Bonazzola
Modified: 2016-06-09 13:33 UTC (History)
11 users (show)

Fixed In Version: rhevm-spice-client-4.0-1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-06-09 13:33:49 UTC
oVirt Team: Spice
Target Upstream Version:


Attachments (Terms of Use)

Description Sandro Bonazzola 2016-02-19 12:47:30 UTC
Build spice-client-msi for RHEL 7 RHEV 4.0

Comment 1 David Blechter 2016-02-19 13:00:28 UTC
(In reply to Sandro Bonazzola from comment #0)
> Build spice-client-msi for RHEL 7 RHEV 4.0

What exactly you are asking? Are you planning to add similar bugs for all RHEVM components?

Comment 2 Sandro Bonazzola 2016-02-26 07:10:51 UTC
(In reply to David Blechter from comment #1)
> (In reply to Sandro Bonazzola from comment #0)
> > Build spice-client-msi for RHEL 7 RHEV 4.0
> 
> What exactly you are asking? Are you planning to add similar bugs for all
> RHEVM components?

Yes, (see https://bugzilla.redhat.com/buglist.cgi?quicksearch=summary%3A"RHEL%207%20RHEV%204.0" )
We need to ensure everything builds in brew for RHEV 4.0 RHEL 7 and we need to have a first test compose for QE.

Comment 3 Sandro Bonazzola 2016-03-07 11:48:40 UTC
ETA for having the build?

Comment 4 David Blechter 2016-03-10 12:39:34 UTC
(In reply to Sandro Bonazzola from comment #3)
> ETA for having the build?

The target is 4.0, and we are not in the planning phase yet.

Comment 6 Yaniv Lavi 2016-05-09 11:00:08 UTC
oVirt 4.0 Alpha has been released, moving to oVirt 4.0 Beta target.


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