Rawhide's xemacs-21.4.6-8 seems to be missing requirements. After an update from xemacs-21.4.6-7, here's what I get: [scop@bobcat scop]$ xemacs xemacs: error while loading shared libraries: libXm.so.3: cannot open shared object file: No such file or directory This is fixed by installing openmotif-2.2.2-5. There are certainly some other requirements missing from the xemacs RPM (the same problem occurs with libwnn.so.0, fixed by installing FreeWnn-libs), see: [scop@bobcat scop]$ rpm -qRp xemacs-21.4.6-8.i386.rpm info ctags rpmlib(VersionedDependencies) <= 3.0.3-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 rpmlib(CompressedFileNames) <= 3.0.4-1 However, "ldd /usr/bin/xemacs-21.4.6" lists pretty many libs... My system is RH7.2, with some parts updated from Rawhide.
Just verified that "rpm -qR" for xemacs-21.4.6-7.i386.rpm (the older version) gives the expected output with all shared libs listed.
Did you use nodeps? If the you didn't have the library and rpm let you install it, that would be an rpm bug...
No, I didn't use --nodeps (because there are practically no dependencies in the xemacs RPM, so rpm didn't tell me to install what's needed). But please take another look at my previous comments, shouldn't "rpm -qRp xemacs-21.4.6-8.i386.rpm" print out a lot of dependencies for libs too, in addition to "info" and "ctags" and the "rpmlib" stuff? At least "rpm -qRp xemacs-21.1.14-23.7.2.i386.rpm" (from 7.2 updates) does... Might still be an rpm bug, dunno? I have rpm-4.0.4-7x from 7.2 updates installed.
(modified means "fixed, waiting for QA confirmation". Setting to assigned.) It's a bug in rpm. The first three lines of one of the scripts in the package read: : # -*-Perl-*- eval 'exec perl -w -S $0 ${1+"$@"}' # Portability kludge if 0; Rpm's find-requires thinks ":" is the interpreter, and bugs out completely, losing all other dependencies. xemacs-21.4.6-9 has a temporary workaround for this rpm bug (chmod -x this file).
Patch your script to put #!/usr/bin/perl at the beginning of the script.
The existing script works. The bug is in rpm - it getting confused in the first place is a bug itself (although hard to fix), forgetting all other dependencies is a much more severe bug.
The core issue is whether a build should fail because a dependency is malformed. The traditional behavior of rpm is to succeed in building, as there is no definition of well formedness wrto dependency tokens.