Bug 62597 - RPM confusing error message
Summary: RPM confusing error message
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: rpm
Version: 7.2
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jeff Johnson
QA Contact:
URL:
Whiteboard:
: 62634 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-04-02 22:32 UTC by Ben Woodard
Modified: 2008-05-01 15:38 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2002-04-02 22:32:18 UTC
Embargoed:


Attachments (Terms of Use)

Description Ben Woodard 2002-04-02 22:32:14 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/20020326

Description of problem:
This bug may be similar to Bug 20286 which in turn is similar to 2895. However,
this one is much more specific and therefore may have a chance of being fixed. ;-)

If you do not have the rpm-build package installed and try to build a package
you get a confusing error message. For example:

[root@test1 SPECS]# rpm -bp kernel-2.4.spec
kernel-2.4.spec: No such file or directory

when the file kernel-2.4.spec is right there. Strace allows you to realize that
the error message is coming from the fact that rpmb is not being exec'd properly.

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


How reproducible:
Always

Steps to Reproduce:
1.rpm -e rpm-build
2.rpm -Uvh anything.src.rpm
3.rpm -ba /usr/src/redhat/SPECS/anything.spec
	

Actual Results:  anything.spec: No such file or directory


Expected Results:  rpmb: No such file or directory
Please install the rpm-build rpm.

Additional info:

Comment 1 Jeff Johnson 2002-04-03 21:56:11 UTC
The build modes are now in /usr/bin/rpmbuild,
not in /bin/rpm, so the error should be
	-ba: unknown option
or (if rpm-build is not installed)
	bash: rpmbuild: command not found

Legacy code dies a long slow lingering death ...

Comment 2 Jeff Johnson 2002-04-03 22:02:46 UTC
*** Bug 62634 has been marked as a duplicate of this bug. ***


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