Bug 586050

Summary:	Red Hat Enterprise Linux 6 ships without php-imap
Product:	Red Hat Enterprise Linux 6	Reporter:	DIanne Skoll <dfs>
Component:	php	Assignee:	Joe Orton <jorton>
Status:	CLOSED CURRENTRELEASE	QA Contact:	BaseOS QE - Apps <qe-baseos-apps>
Severity:	high	Docs Contact:
Priority:	low
Version:	6.0	CC:	mmckinst, poehler
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	php-5.3.2-3.el6	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-07-02 19:42:16 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:
Bug Depends On:	586875
Bug Blocks:

Description DIanne Skoll 2010-04-26 17:40:33 UTC

Our product (and many others) relies on php-imap.  RHEL6-beta-1 seems to ship without it; I can't find it in the optional repo either.

Regards,

David.

Comment 2 RHEL Program Management 2010-04-26 19:22:21 UTC

This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.

Comment 4 DIanne Skoll 2010-06-14 21:05:37 UTC

Hi,

Any decision yet?  Without php-imap, we will have to drop Red Hat Enterprise Linux from our list of supported distributions.  We need to give our customers a heads-up, so as soon as you make your decision, I'd appreciate knowing it.

Regards,

David.

Comment 5 Joe Orton 2010-06-15 07:39:18 UTC

php-imap is included in current internal builds of php.  A test build is available from:

http://people.redhat.com/jorton/Santiago/

Comment 6 DIanne Skoll 2010-06-15 13:49:09 UTC

Thank you... our software installs now.

Comment 8 releng-rhel@redhat.com 2010-07-02 19:42:16 UTC

Red Hat Enterprise Linux Beta 2 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.