-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

while building packages I found that the automatic mechanism for finding out 
package Requires/Provides is not working when I use »/usr/lib/rpm/rpmdeps«. 
However, the find-{requires,provides} scripts work, but as far as I know they 
do not examine the package for perl, python, ... dependencies. I also read 
somewhere that the »rpmdeps« binary is the preferred way of handling 
dependency generation.

To give some example: I have a package called "samba-libs" which carries the 
following files:

$ rpm -ql samba-libs
(...)
/usr/lib/libmsrpc.a
/usr/lib/libmsrpc.so
/usr/lib/libsmbclient.a
/usr/lib/libsmbclient.so
/usr/lib/libsmbsharemodes.a
/usr/lib/libsmbsharemodes.so
/usr/lib/samba
/usr/lib/samba/auth
/usr/lib/samba/auth/script.so
/usr/lib/samba/charset
/usr/lib/samba/charset/CP437.so
/usr/lib/samba/charset/CP850.so
/usr/lib/samba/idmap
/usr/lib/samba/lowcase.dat
/usr/lib/samba/upcase.dat
/usr/lib/samba/valid.dat
(...)

Using "rpmdeps -R" on this list gives simply nothing:
$ rpm -ql samba-libs | /usr/lib/rpm/rpmdeps -R
$

However, find-requires gives a lot of output:

$ rpm -ql samba-libs | /usr/lib/rpm/find-requires
libasn1.so.6
libc.so.6
libc.so.6(GLIBC_2.0)
(...)
librt.so.1
librt.so.1(GLIBC_2.1)
$

The behaviour occurred in RPM version 4.4.6 and 4.4.8. On my fedora laptop, 
where RPM version 4.4.2 is installed, the rpmdeps binary works as expected. 
Of course, the two files carry huge differences.

I have simply no idea where to start searching for the actual problem. I 
thought upgrading would do, but after installing version 4.4.8, it didn't 
work out. I'd be glad to supply any information needed, but I'm totally 
beeing groping in the dark.

Sincereley,
	Eric
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)

iD8DBQFGlSV2fkUtd7QNU/sRAsK2AJsFUX1PzjrBJvA7MXioncc1XlOr+ACcCS++
i6yfl9Fe/DmWoRlryabDWwA=
=TEFm
-----END PGP SIGNATURE-----