Bug 1448466

Summary:	please update to 1.4.9
Product:	[Fedora] Fedora EPEL	Reporter:	Matthias Runge <mrunge>
Component:	python-amqp	Assignee:	Eric Harney <eharney>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	epel7	CC:	eharney, fschwarz, Marcin.Dulak, projects.rg
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	python-amqp-1.4.9-1.el7	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-03-06 17:29:48 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:	1329587

Description Matthias Runge 2017-05-05 13:21:27 UTC

Description of problem:
updating kombu to a version of 3.x requires amqp >= 1.4.9

Version-Release number of selected component (if applicable):
epel7 has currently 1.4.5 (or 1.4.6, if packages in epel7-testing count as well)

Comment 1 marcindulak 2017-12-08 13:45:01 UTC

Since there is a recent activity on Fedora, is there a chance to update in EPEL7?

Comment 2 Fedora Update System 2018-01-03 15:57:50 UTC

python-amqp-1.4.9-1.el7 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-73496795c8

Comment 3 Fedora Update System 2018-01-03 21:45:39 UTC

python-amqp-1.4.9-1.el7 has been pushed to the Fedora EPEL 7 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-73496795c8

Comment 4 Fedora Update System 2018-03-06 17:29:48 UTC

python-amqp-1.4.9-1.el7 has been pushed to the Fedora EPEL 7 stable repository. If problems still persist, please make note of it in this bug report.