Bug 7324

Summary: rpm build stops, no error reported.
Product: [Retired] Red Hat Linux Reporter: robert
Component: rpmAssignee: Jeff Johnson <jbj>
Status: CLOSED NOTABUG QA Contact:
Severity: low Docs Contact:
Priority: medium    
Version: 6.1   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 1999-11-27 10:36:57 EST Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description robert 1999-11-25 06:53:22 EST
I managed to confuse rpm with some general stupidity:

The install section of my spec file made incorrect links for a dynamic
library. Something like:

$ ls -al
/usr/lib/libestjava.so.1 -> libestbase.so.1.2*
/usr/lib/libestjava.so.1.2 -> libestbase.so.1.2.1*
/usr/lib/libestjava.so.1.2.1->libestbase.so.1.2.1.1*
/usr/lib/libestjava.so.1.2.1.1*

(don't ask why we've got 4 numbers in library names)

When RPM got to the finding dependency stage it just stopped without
building packages, and reported no errors.

It isn't a great problem, just not getting an error message meant it took
me a while to track the problem down...

Regards,
Rob Clark.
CSTR, University of Edinburgh
Comment 1 Jeff Johnson 1999-11-27 10:36:59 EST
RPM always reports errors, but the error message is often not the last
line on the screen. Go back through the output and you'll find the packaging
error.