[root@nostromo i386]# rpm -q --conflicts bar ook [root@nostromo i386]# rpm -q --requires bar rpmlib(PayloadFilesHavePrefix) <= 4.0-1 rpmlib(CompressedFileNames) <= 3.0.4-1 [root@nostromo i386]# rpm -q ook bar ook-0.10-0.testing.1 bar-0.10-0.testing.1 [root@nostromo i386]# rpm -V bar Unsatisfied dependencies for bar-0.10-0.testing.1.i386: ook Surely that should say something like: Unsatisfied dependencies for bar-0.10-0.testing.1.i386: bar conflicts with ook Version-Release number of selected component (if applicable): [root@nostromo i386]# rpm -q rpm rpm-4.4.2-7
The information regarding whether it's a Requires: or a Conflicts: is in lib/verify.c:443 /* XXX FIXME: should probably supply the "[R|C] " type prefix */ I. e. R and C indicate whether it is a Requires: or Conflicts: failure. The problem is conforming with ageless user expectations and API's (a similar problem exists returning arch info through rpm-python) . The behavior in rpm is same as always, and increasingly useless and broken. E.g. yopu expectation seesm to indicate that packages "conflicts" and "with" have missing dependencies while the package "bar" is self conflicting
Perhaps this output is more to your liking: Unsatisfied dependencies for rpm-devel-4.4.3-0.46.i386: Requires: libtool(/usr/lib/libbeecrypt.la) Requires: libtool(/usr/lib/libexpat.la) Requires: libtool(/usr/lib/libneon.la) Requires: libtool(/usr/lib/librpmdb.la) Requires: libtool(/usr/lib/librpmio.la) Requires: libtool(/usr/lib/libsqlite3.la) Unsatisfied dependencies for apr-util-devel-0.9.7-4.i386: Requires: libtool(/usr/lib/libapr-0.la) Requires: libtool(/usr/lib/libexpat.la) Fixed in CVS, will be in rpm-4.4.3-0.48 when built.
Created attachment 121003 [details] [PATCH] display -Va dependency failures as Requires: or Conflicts: (#172878). display -Va dependency failures as Requires: or Conflicts: (#172878).