Bug 1017965

Summary:	Enable testsuite during build in %check phase for autoconf213
Product:	Red Hat Enterprise Linux 7	Reporter:	Pavel Raiskup <praiskup>
Component:	autoconf213	Assignee:	Pavel Raiskup <praiskup>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Martin Cermak <mcermak>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.0	CC:	mcermak, mfranc, ovasik, qe-baseos-tools-bugs
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-06-13 12:31:24 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:

Description Pavel Raiskup 2013-10-10 20:57:37 UTC

I recently enabled testsuite for autoconf213 (which is still needed to rebuild
firefox and some related projects) in Fedora Rawhide.  This bug is mentioned
to ask QA whether they think that it does make sense to enable the testsuite
also in RHEL7 or not for this legacy tool (this action requires respin); and
to track the enablement if yes.  Note that the package shouldn't be used by
our customers.

I know that there are concerns to enable upstream testsuites if possible, I'm
just not sure if we should do it really everywhere.

This bug may be closed by QA as WONTFIX, if there is no need to do so.

Comment 2 Martin Cermak 2013-10-11 07:35:49 UTC

From my point it's definitely useful to have the testsuite enabled by default: This way eventual issues will appear right at the build time. Creating an erratum just because of this doesn't seem reasonable to me, but please do so once some erratum for this component comes. Thanks.

Comment 4 Pavel Raiskup 2013-10-18 12:30:37 UTC

http://bulk-mail.corp.redhat.com/archives/cvs-commits-list/2013-October/msg06937.html

Comment 7 Ludek Smid 2014-06-13 12:31:24 UTC

This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.