Bug 1017965 - Enable testsuite during build in %check phase for autoconf213
Summary: Enable testsuite during build in %check phase for autoconf213
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: autoconf213
Version: 7.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Pavel Raiskup
QA Contact: Martin Cermak
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-10 20:57 UTC by Pavel Raiskup
Modified: 2014-06-18 05:06 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-13 12:31:24 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

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.
Note You need to log in before you can comment on or make changes to this bug.