Red Hat Bugzilla – Bug 55233
trying to use rpm flags implemented in rpm-build when not installed gives confusing error message
Last modified: 2008-05-01 11:38:01 EDT
Description of Problem: When I try to use any of the rpm options that are implemented by the rpm-build package without having the rpm-build package installed i get the following (confusing) error message: packagename-1-1.src.rpm: No such file or directory Version-Release number of selected component (if applicable): Standard redhat-7.2. [noa@localhost noa]$ rpm -q rpm rpm-4.0.3-1.03 How Reproducible: Always Steps to Reproduce: 1. make sure rpm-build is not installed 2. fetch an src rpm 3. try to rebuild it (rpm --rebuild package-1-1.src.rpm) Actual Results: [noa@localhost noa]$ LANG=C rpm --rebuild msttcorefonts-1-1.src.rpm msttcorefonts-1-1.src.rpm: No such file or directory Expected Results: Perhaps something along the lines of [noa@localhost noa]$ LANG=C rpm --rebuild msttcorefonts-1-1.src.rpm Error: you neeed to install the rpm-build package to use the --rebuild option Additional Information: A strace shows that rpm blindly tries to open rpmb execve("/usr/lib/rpm/rpmb", ["/usr/lib/rpm/rpmb", "--rebuild", "msttcorefonts-1-1.src.rpm"], [/* 23 vars */]) = -1 ENOENT (No such file or directory) Which fails.
The build modes have moved out of /bin/rpm, invoke /usr/bin/rpmbuild instead.
The confusing error message is still a problem though. I would be very happy if /bin/rpm just removed all build related options, or even better replaced them with a standard error message pointing towards /usr/sbin/buildrpm instead. This might not be convinient, but at least the behaviour is clear.