Red Hat Bugzilla – Bug 12853
Funnies w/ installer's rpm on RH6.x system
Last modified: 2005-10-31 17:00:50 EST
( I'm not sure where to file this, but here it goes under installer with
Cc: to jbj)
Funnies happen if you copy RedHat/instimage/usr/bin/rpm over to a RH6x
system to be able to query packages etc.:
[root@linftp bin]# ./rpm -qi kernel
error: cannot open file kernel: No such file or directory
'rpm -q --info kernel' works fine, as does 'rpm -q kernel'.
There may be other issues like this, I didn't check all the possibilities.
Please note that copying /bin/rpm from a fresh beta2 install works
properly. This looks interesting, because both seem to be static binaries,
but the /bin/rpm is 886k while the instimage ver is 1343k..
Instimage version works fine on beta2 install.
That isn't going to work right; even though it's statically linked, it's
against a different libc; also, it's a different version of RPM, and so it
expects a different configuration; the querying stuff in RPM is actually
done with separate executables by popt magic.
Ok, I don't know the internals of RPM, but the main issue (apart from general
wondering still remains).
That is, 'rpm -qi' (rpm from instimage) won't work on RH62, even though 'rpm -q
--info' does. The same functionatily there, so fixing it probably shouldn't be
a big problem.
This is almost certainly tied closely to #12027 (similar, but slightly different
stuff w/ beta1).
This is more of an rpm issue than installer issue.
Similar things happen with beta3 too; for example, rpm --info is not recognized.
This isn't really an rpm bug, but rather an issue with the environment in which
Even though rpm is statically linked, several helper functions and a popt
to re-exec the helper functions are now needed to do anything but
(and some of the options used by install/upgrade are also now implemented with
If this is still in issue, please change the component to anaconda, as the fix
setting up suffcient environment in the installer to execute rpm.
Changed component to anaconda as suggested.
The behaviour still persists with beta4.