Validating your RPM dependency tree

| | Comments (1)

Have you ever wondered if your RPM dependency tree had any holes? It shouldn't have any holes if you have never used --nodeps.

On a FC3 box that I was building and installing rawhide packages for GNOME v2.10 I was forced to use --nodeps to get packages installed. Later dependencies were satisfied. I wanted to see if I had any holes left.

Here how I did it:


# rpm -Va 2>&1 | grep "Unsatisfied dependencies"
Unsatisfied dependencies for rhn-applet-2.1.16-1.i386: gnome-python2-gtkhtml2
Unsatisfied dependencies for system-config-printer-gui-0.6.116.1.1-1.i386: gnome-python2-gtkhtml2
Unsatisfied dependencies for openoffice.org-1.1.3-9.5.0.fc3.i386: libebook.so.8, libedataserver.so.3
Unsatisfied dependencies for bluez-pin-0.24-1.i386: libdbus-1.so.0, libdbus-glib-1.so.0

The -V option really needs a --just-check-deps or something as this takes a LONG time to run with all the md5 and file validation.

1 Comments

Hey Dax!

I was searching for the Guru RPM guide, and hit this instead.... Fun to see the pics of Bryan with headphones on like usual :-)

What you want is something like

[root@mingus ~]# rpm -Va --nofiles --noscripts --nodigest --nosignature --nolinkto --nomd5 --nosize --nouser --nogroup --nomtime --nomode --nordev
[root@mingus ~]#

I highly recommend defining that as an alias for the sake of your fingers and sanity....

Leave a comment

About this Entry

This page contains a single entry by Dax published on March 25, 2005 5:13 PM.

Advanced Wi-Fi was the previous entry in this blog.

New rdesktop version is the next entry in this blog.

Find recent content on the main index or look in the archives to find all content.