Bug 2877

Summary:	check_elf_files fails with filenames containing parentheses
Product:	Mageia	Reporter:	Matteo Pasotti <matteo.pasotti>
Component:	RPM Packages	Assignee:	D Morgan <dmorganec>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Normal	CC:	marja11, stormi-mageia
Version:	1
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:	spec-helper-0.31.5-2.mga1	CVE:
Status comment:
Attachments:	A patch that solve this bug

Description Matteo Pasotti 2011-09-30 09:32:00 CEST

Description of problem:
Building a package that contains files named like foobar().html , make the script /usr/share/spec-helper/check_elf_files fail without exiting and making the building process to wait infinitely.

Version-Release number of selected component (if applicable):
The header of the file reports 
$Id: check_elf_files 266655 2010-03-05 12:59:47Z peroyvind

How reproducible:
Try to build sdlbasic package (http://svnweb.mageia.org/packages/cauldron/sdlbasic/)

Error I receive:
sh: -c: line 0: syntax error near unexpected token `('
sh: -c: line 0: `file -- waitKey().html'
sh: -c: line 0: syntax error near unexpected token `('
sh: -c: line 0: `file -- key().html'


Steps to Reproduce:
1. install rpm-build or bm
2. mgarepo co sdlbasic
3. cd sdlbasic && bm -bl

This bug affects not only cauldron but Mageia 1, too.

Comment 1 Matteo Pasotti 2011-09-30 09:33:58 CEST

Created attachment 864 [details]
A patch that solve this bug

Comment 2 Samuel Verschelde 2011-10-01 03:13:20 CEST

Assigning to maintainer now that our maintainers database has an entry for
this package. Please assign back to bugsquad@mageia.org in case of a mistake
from me.

There is a patch.

CC: (none) => stormi
Version: Cauldron => 1
Assignee: bugsquad => dmorganec

Comment 3 D Morgan 2011-12-13 09:32:11 CET

seems OK for me.

Boklm, can you check too please ?

CC: (none) => boklm

Comment 4 Marja Van Waes 2012-03-15 21:08:48 CET

(In reply to comment #3)
> seems OK for me.
> 
> Boklm, can you check too please ?

Boklm?

Pinging, because nothing has happened with this report for more than 3 months, it still has the status NEW or REOPENED.

CC: (none) => marja11

Comment 5 Marja Van Waes 2012-07-06 15:05:20 CEST

Please look at the bottom of this mail to see whether you're the assignee of this  bug, if you don't already know whether you are.


If you're the assignee:

We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead.

If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard.

Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why.

Thanks :)

**************************** 

@ the reporter and persons in the cc of this bug:

If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us.

@ the reporter of this bug

If you didn't reply yet to a request for more information, please do so within two weeks from now.

Thanks all :-D

Comment 6 Matteo Pasotti 2012-07-07 22:19:52 CEST

This bug seems fixed to me. You could mark it as resolved fixed.

Comment 7 Marja Van Waes 2012-07-07 22:28:57 CEST

(In reply to comment #6)
> This bug seems fixed to me. You could mark it as resolved fixed.

OK, thanks.

As far as I know you're the only one who reported it, there are no "me too."s in this report

Status: NEW => RESOLVED
Resolution: (none) => FIXED

Nicolas Vigier 2014-05-08 18:06:14 CEST

CC: boklm => (none)