Bug 430082

Summary:	Please rebuild asterisk for EPEL 4 and 5
Product:	[Fedora] Fedora	Reporter:	Robert Scheck <redhat-bugzilla>
Component:	asterisk	Assignee:	Jeffrey C. Ollie <jeff>
Status:	CLOSED CANTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	low
Version:	rawhide	CC:	robert.scheck
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-02-13 18:20:51 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:	430080, 430081
Bug Blocks:

Description Robert Scheck 2008-01-24 13:59:08 UTC

Description of problem:
Please rebuild asterisk for EPEL 4 and 5

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

Actual results:
No asterisk in EPEL 4 and 5

Expected results:
Package asterisk in EPEL 4 and 5

Additional info:
Please let me know, when you're not interested in maintaining the package 
there.

Comment 1 Robert Scheck 2008-01-24 14:00:18 UTC

I filed bug reports for all unsatisfied dependencies. Hopefully, I didn't 
forget anything - otherwise please correct.

Comment 2 Jeffrey C. Ollie 2008-01-24 18:56:56 UTC

I have no interest at all in maintaining Asterisk for EPEL 4 as I have no RHEL 4
systems.  If the Speex issue can be resolved I will be maintaining Asterisk for
EPEL 5.  For the time being I'm maintaining a private repository for Asterisk here:

http://repo.ocjtech.us/misc/epel/5/

Comment 3 Jeffrey C. Ollie 2008-02-13 18:20:51 UTC

Closing this as it seems the speex issue won't be resolved before RHEL6.

Comment 4 Robert Scheck 2008-02-13 18:50:34 UTC

Can't we ship a private/internal speex up2date enough inside of asterisk 
package?

Comment 5 Jeffrey C. Ollie 2008-02-13 19:11:38 UTC

(In reply to comment #4)
> Can't we ship a private/internal speex up2date enough inside of asterisk 
> package?

No, EPEL policy prohibits that sort of behavior.