Bug 246614 - mock doesn't report rpmbuild error
Summary: mock doesn't report rpmbuild error
Status: CLOSED DUPLICATE of bug 244596
Alias: None
Product: Fedora Hosted Projects
Classification: Retired
Component: mock   
(Show other bugs)
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Clark Williams
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-07-03 13:10 UTC by Jeff Sheltren
Modified: 2013-01-10 04:22 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2007-07-18 12:46:30 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description Jeff Sheltren 2007-07-03 13:10:03 UTC
When building a package with the latest mock version, mock-0.7.2-1.fc6.1,
rpmbuild errors don't get caught by mock - it exits normally.

Version-Release number of selected component (if applicable):
mock-0.7.2-1.fc6.1

How reproducible:
Always

Steps to Reproduce:
1. Create an SRPM which would generate rpmbuild errors (example: installed file
not listed in %files)
2. Run mock to build that SRPM
  
Actual results:
mock exits with 0 status, no error messages printed out:
----------
init
clean
prep
This may take a while
unpack cache
setup
build
ending
done
Results and/or logs in: /var/lib/mock/fedora-6-i386-core/result

$ echo $?
0

$ tail -3 /var/lib/mock/fedora-6-i386-core/result/build.log 
RPM build errors:
    Installed (but unpackaged) file(s) found:
   /etc/yum.repos.d/cs-testing.repo
----------


Expected results:
mock should report/display rpmbuild error and exit with some error code.

Comment 1 Mohd Izhar Firdaus Ismail 2007-07-03 13:14:18 UTC
I'm getting the same problem with mock-0.7.2-1.fc7

Comment 2 Jeff Sheltren 2007-07-18 12:46:30 UTC

*** This bug has been marked as a duplicate of 244596 ***


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