Bug 147383

Summary: wrong "file not found by glob" error
Product: Red Hat Enterprise Linux 3 Reporter: Alexander Suvorov <say>
Component: rpmAssignee: Panu Matilainen <pmatilai>
Status: CLOSED WONTFIX QA Contact: Mike McLean <mikem>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.0CC: nobody+pnasrat, say, tim.nelson
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: 2007-10-19 19:07:37 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
spec file for testing bug
none
patch that fixes the bug none

Description Alexander Suvorov 2005-02-07 19:54:12 UTC 
Description of problem: 
we can't use files with special wildcard symbols as regular files in 
%files section of spec-file. I.e. file "test-*.txt" 
when we try to add to rpm such file we get message: 
 
error: File not found by glob: <filename> 
 
 
Version-Release number of selected component (if applicable): 
rpm-4.2.3-13 
 
How reproducible: 
Every time 
 
Steps to Reproduce: 
1. get attached test.spec file 
2. run rpmbuild -bb test.spec 
3. we've got an error 
   
Actual results: 
we've got an error: 
error: File not found by glob: <filename> 
 
Expected results: 
the rpm must be built succesfully 
 
Additional info: 
I include a simple patch that fixes this bug, but I don't sure that 
this extra check of myGlobPatternP(argv[0]) is completely 
unnecessary. 
 
So, if this check is needed for rpm correct working, please, find 
another way to fix error in processing files with wildcard-symbols 
in it's name. 
 
Patch must be appled to the file build/files.c
Comment 1 Alexander Suvorov 2005-02-07 19:57:47 UTC 
Created attachment 110745 [details]
spec file for testing bug
Comment 2 Alexander Suvorov 2005-02-07 19:58:48 UTC 
Created attachment 110746 [details]
patch that fixes the bug
Comment 3 Tim Nelson 2005-04-06 07:11:51 UTC 
Is this at all related to bug #139460 ?  Because I'm experiencing the problem
mentioned in that bug, but on Redhat Enterprise instead of Fedora.
Comment 4 Jeff Johnson 2007-01-03 17:18:57 UTC 
Fixed in rpm cvs, will be in rpm-4.4.8-0.9 when built.

UPSTREAM
Comment 5 RHEL Program Management 2007-10-19 19:07:37 UTC 
This bug is filed against RHEL 3, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products. Since
this bug does not meet that criteria, it is now being closed.
 
For more information of the RHEL errata support policy, please visit:
http://www.redhat.com/security/updates/errata/
 
If you feel this bug is indeed mission critical, please contact your
support representative. You may be asked to provide detailed
information on how this bug is affecting you.