Bug 531470

Summary:	Update libmicrohttpd for EL5 to latest release
Product:	[Fedora] Fedora EPEL	Reporter:	Tim Niemueller <tim>
Component:	libmicrohttpd	Assignee:	Erik van Pienbroek <erik-fedora>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	low
Version:	el5	CC:	erik-fedora
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	libmicrohttpd-0.4.6-1.el5	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-07-30 01:03:39 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Tim Niemueller 2009-10-28 14:17:25 UTC

Description of problem:
Currently libmicrohttpd 0.3.1 is provided for RHEL, the newest version 0.4.2 provides significantly improved features. Therefore I kindly request to upgrade libmicrohttpd to the latest release 0.4.2 for EPEL5.

As far as I can tell (repoquery --whatrequires libmicrohttpd) there is no software currently packaged in EPEL depending on this library and hence such an update should be safe.

Comment 1 Fedora Update System 2010-07-04 15:28:10 UTC

libmicrohttpd-0.4.6-1.el5 has been submitted as an update for Fedora EPEL 5.
http://admin.fedoraproject.org/updates/libmicrohttpd-0.4.6-1.el5

Comment 2 Fedora Update System 2010-07-09 05:59:13 UTC

libmicrohttpd-0.4.6-1.el5 has been pushed to the Fedora EPEL 5 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update libmicrohttpd'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/libmicrohttpd-0.4.6-1.el5

Comment 3 Fedora Update System 2010-07-30 01:03:30 UTC

libmicrohttpd-0.4.6-1.el5 has been pushed to the Fedora EPEL 5 stable repository.  If problems still persist, please make note of it in this bug report.