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
rpm files aren't coped because of a bad glob value in the mock script.
expected the rpm files to be copied to the result directory too
Created attachment 131478 [details]
the attached patch fixes all version 0.4.8 and later
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.
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.
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"