Bug 1036389

Summary:	Please build latest libsidplay for EPEL 6
Product:	[Fedora] Fedora	Reporter:	Robert Scheck <redhat-bugzilla>
Component:	libsidplay	Assignee:	Orphan Owner <extras-orphan>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	22	CC:	extras-orphan
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:	2016-07-19 19:27:45 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:
Bug Depends On:
Bug Blocks:	1036388

Description Robert Scheck 2013-12-01 19:57:25 UTC

Description of problem:
Please build latest libsidplay for EPEL 6, because it is a build and run-time
dependency of audacious-plugins. Just rebuilding the libsidplay-1.36.60-5.fc18 
package seems to be sufficient.

Version-Release number of selected component (if applicable):
libsidplay-1.36.60-5.fc18

Actual results:
No libguess in EPEL 6

Expected results:
libsidplay-1.36.60-1.el6 or better ;-)

Additional info:
Please let me know if you are not interested in maintaining the package.

Comment 1 Jaroslav Reznik 2015-03-03 15:14:52 UTC

This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22

Comment 2 Fedora End Of Life 2016-07-19 19:27:45 UTC

Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.