Bug 196537

Summary: rpm files not copied to resultdir
Product: [Fedora] Fedora Reporter: Jim Richardson <treyvan>
Component: mockAssignee: David Cantrell <dcantrell>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: medium    
Version: 5CC: extras-qa
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: 2006-06-24 21:44:51 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
the attached patch fixes all version 0.4.8 and later none

Description Jim Richardson 2006-06-24 05:01:51 UTC 
Description of problem: when building a package with mock and specifying the
output directory via --resultdir the src.rpm is copied to the result directory
but not the rpm files.


Version-Release number of selected component (if applicable):
0.4.8 and later

How reproducible: always


Steps to Reproduce:
1. build a package with mock --resultdir defaultresult/packagename
2. logs and src.rpm are in the resultdir but not rpm files
3.
  
Actual results: 

rpm files aren't coped because of a bad glob value in the mock script.



Expected results:
expected the rpm files to be copied to the result directory too

Additional info:
Comment 1 Jim Richardson 2006-06-24 05:01:51 UTC 
Created attachment 131478 [details]
the attached patch fixes all version 0.4.8 and later
Comment 2 Jesse Keating 2006-06-24 14:15:41 UTC 
Can you retry this with 0.6-4?  Upstream mock released 0.6 a week or 2 ago, and
I finally got a package that works right built yesterday.
Comment 3 Jim Richardson 2006-06-24 16:35:25 UTC 
The latest upstream version I can find is mock-0.6.3, and yes the but still
exists there. As a matter of fact upgrading to these latest version broke my
mock and I had research all over again to find my previous patch that I forgot
to report at the time.

If you peek at the patch you'll see the one-liner is really a "no-brainer", a I
suppose the fact that I am not using mock in "extras" and wrote a collection
script to deal with results is the reason this bug hasn't been reported by others.
Comment 4 Jim Richardson 2006-06-24 18:21:22 UTC 
I guess I need to revoke my previous comment. After cleaning a build root, the
newly initialized buildroot did solve the problem albeit in a manner which
causes my fix to fail.

Therefore, at this time I do beleive this issue can be closed with a status of
"NOT A BUG"