Red Hat Bugzilla – Bug 56636
--nodeps option has no effect.
Last modified: 2008-05-01 11:38:01 EDT
Description of Problem:
I typed this:
rpm --root /root/for/embedded/system -Uvh ../RPMS/pciutils-2.1.5-2.i386.rpm
and got failed dependencies.
When I use the "--nodeps" flag, I get *exactly the same* failed dependencies.
I am trying to install some RH6.2 RPMS into a root directory which will
form the image of an embedded system. Using RPM 4.0.2 on RH6.2, the
install works fine. Using RPM 4.0.3 on RH7.2, the --nodeps option fails
and the system will not install the packages. The root directory has been
prepared with rpm --initdb.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. mkdir /temp
2. rpm --initdb --root /temp
3. rpm --Uvh --root /temp --nodeps any_package_with_dependencies.rpm
Dependency checks failed and installation was aborted.
Dependency checks should have been ignored.
What happens if you do a rpm --rebuilddb?
Do the missing dependencies reappear?
If I do rpm --rebuilddb, the effect is the same. The dependencies really *are*
missing, but I do not care. I want RPM to do the installation anyway. RPM
4.0.2 on Red Hat 6.2 works; RPM 4.0.3 on Red Hat 7.2 appears to ignore the
Hmmm, --nodeps "works" in rpm-4.0.3 with --root, I use it hourly.
Try putting --nodeps immediately after -Uvh, rpm options now
require that the mode be the 1st option in order to support
multimode CLI options in the future.
That fixed it. Putting "-Uvh" first makes it work. Thanks.
Hmm, I was just bittne by this as well (I don't have a redhat kernel, since
they still dont ship with freeswan) and therefor I'm lacking the kernel
dependancy, so i had to force iptables to install.
Why is this bug closed? It seems that the order of options of rpm really
shouldn't matter, and this is a bug that should be fixed.
The order of options is going to matter a great deal
when I finish doing multi-mode options like
rpm -Uvh ... -qa ... -Va ... -e ...
I gotta start someplace ...