Bug 51727
Summary: | rpm 4.0.2 returns 0 status despite error message | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Tim Freeman <tim> |
Component: | rpm | Assignee: | Jeff Johnson <jbj> |
Status: | CLOSED WORKSFORME | QA Contact: | David Lawrence <dkl> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 6.1 | ||
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: | 2001-08-14 14:23:11 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: |
Description
Tim Freeman
2001-08-14 14:23:06 UTC
The exit status of rpm has always been the number of failed operations/objects, not a boolean "bad operation" like many programs return. In addition, --target is not actually known to the /bin/rpm executable, it's a configurable popt alias that execs /usr/bin/rpmbuild. That executable returns a non-zero exit status: bash$ rpmbuild --target || echo yeah --target: missing argument yeah In fact, it looks like you have not installed the rpm-build package |