Bug 739644 - espeak 1.45.05-2 not built with $RPM_OPT_FLAGS
espeak 1.45.05-2 not built with $RPM_OPT_FLAGS
Product: Fedora
Classification: Fedora
Component: espeak (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Jaroslav Škarvada
Fedora Extras Quality Assurance
: Patch, Regression
Depends On:
Blocks: DebugInfo
  Show dependency treegraph
Reported: 2011-09-19 13:35 EDT by Ville Skyttä
Modified: 2011-09-19 16:13 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2011-09-19 14:40:43 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Build with $RPM_OPT_FLAGS and $RPM_LD_FLAGS (1.22 KB, patch)
2011-09-19 13:35 EDT, Ville Skyttä
no flags Details | Diff

  None (edit)
Description Ville Skyttä 2011-09-19 13:35:43 EDT
Created attachment 523877 [details]

espeak 1.45.05-2 is not built with $RPM_OPT_FLAGS; 1.43-4 did not have this problem.


Fix attached.  Regarding $RPM_LD_FLAGS this patch adds "while at it", see http://lists.fedoraproject.org/pipermail/devel/2011-August/155358.html
Comment 1 Jaroslav Škarvada 2011-09-19 14:40:43 EDT
Ville thanks, applied.

Kamil, such regressions could be caught automatically, couldn't it?
Comment 2 Ville Skyttä 2011-09-19 15:32:05 EDT
I have submitted the script I use to look for problems like this (and which in fact caught this one) to AutoQA about 2 years ago but not much has happened: https://fedorahosted.org/autoqa/ticket/59

Also, rpmlint has issued errors for empty debuginfo packages and ones without sources for a long time, those too would have caught this one.
Comment 3 Kamil Páral 2011-09-19 16:13:05 EDT
Unfortunately we currently don't have resources to execute these tests. Loads of new proposed test cases, unfinished software architecture and scarce development power. Very sorry :-/

Note You need to log in before you can comment on or make changes to this bug.