Bug 973014

Summary:	Building python-daemon for 3.3
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Kiril Nesenko <knesenko>
Component:	Build Subsystem	Assignee:	Kiril Nesenko <knesenko>
Status:	CLOSED ERRATA	QA Contact:	Jiri Belka <jbelka>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	3.3.0	CC:	acathrow, cboyle, dfediuck, eedri, iheim, jkt, knesenko, mgoldboi, pstehlik, Rhev-m-bugs, srevivo, yeylon
Target Milestone:	---	Keywords:	Triaged
Target Release:	3.3.0	Flags:	cboyle: needinfo-
Hardware:	x86_64
OS:	Linux
Whiteboard:	integration
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-01-21 14:48:00 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:

Description Kiril Nesenko 2013-06-11 05:05:18 UTC

Description of problem:
This bug is needed for building python-lockfile and python-daemon for RHEVM 3.3

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 Itamar Heim 2013-08-27 17:44:20 UTC

how can we have a single bug/errata for two separate packages?

Comment 3 Kiril Nesenko 2013-08-28 04:20:35 UTC

(In reply to Itamar Heim from comment #2)
> how can we have a single bug/errata for two separate packages?

This bug will be used for python-daemon only. For python-lockfile - https://bugzilla.redhat.com/show_bug.cgi?id=976405 .

I will change the bug summary accordingly.

Comment 4 Jiri Belka 2013-10-30 12:33:36 UTC

ok, is20.1.

Comment 5 Charlie 2013-12-06 01:55:38 UTC

Does this require doc text? thanks?

Comment 6 Kiril Nesenko 2013-12-08 11:06:42 UTC

(In reply to Charlie from comment #5)
> Does this require doc text? thanks?

No need.

- Kiril

Comment 8 errata-xmlrpc 2014-01-21 14:48:00 UTC

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.

http://rhn.redhat.com/errata/RHBA-2014-0056.html