Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 85024 - rpm --rebuild fails with useless error message if rpm-build is not installed
Summary: rpm --rebuild fails with useless error message if rpm-build is not installed
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 2.1
Classification: Red Hat
Component: rpm
Version: 2.1
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jeff Johnson
QA Contact: Mike McLean
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-02-24 22:17 UTC by Lee Sheridan
Modified: 2007-11-30 22:06 UTC (History)
0 users

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2003-02-24 23:14:21 UTC


Attachments (Terms of Use)

Description Lee Sheridan 2003-02-24 22:17:06 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1) Gecko/20021007
Debian/1.1-1

Description of problem:
[root@machine root]# rpm --rebuild php-4.2.2-8.0.7.src.rpm
php-4.2.2-8.0.7.src.rpm: No such file or directory


Installing "rpm-build" fixes the problem, but the error message could be much
more useful if it complained about being able to find files from rpm-build or
told me to try installing that RPM.

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


How reproducible:
Always

Steps to Reproduce:
1.Install a system without rpm-build
2.Try to build a .src.rpm file using "rpm --rebuild testfile.src.rpm".  Note the
misleading error message.
3.Install the "rpm-build" package and try step 2 again, which will work.
    

Additional info:

Comment 1 Jeff Johnson 2003-02-24 23:14:21 UTC
This already fixed in rpm-4.1 by putting rpm build
modes into a seperate /usr/bin/rpmbuild executable.


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