Hi: I maintain the open-iscsi package. It delivers the PRMs: - libopeniscsiusr0_2_0 - open-iscsi-2.1.8 - open-iscsi-devel-2.1.8 My problem is with libopeniscsiusr0_2_0. And this problem only seems to occur on SUSE's Internal Build Service, but I'm hoping you can help anyway. My libopeniscsiusr package has only two files in it: a shared library, and a symlink to that library. Here are the two after %build:
lrwxrwxrwx 1 lduncan 24 Dec 9 12:21 libopeniscsiusr.so.0 -> libopeniscsiusr.so.0.2.0* -rwxr-xr-x 1 lduncan 143424 Dec 9 12:21 libopeniscsiusr.so.0.2.0*
So libopeniscsiusr.so.0 is a symlink to libopeniscsiusr.so.0.2.0, the real shared library. [A development package adds the "libopeniscsiusr.so" symlink] In my RPM SPEC file, I specify the files in the library RPM like this:
%files -n libopeniscsiusr0_2_0 %{_libdir}/libopeniscsiusr.so.*
And when the RPM is built and I examine it (or install it), sure enough the package is installed correctly, in /usr/lib64, i.e. libopeniscsiusr.so.0 is a symlink to libopeniscsiusr.so.0.2.0. As I said, our open build service handles this fine. But when I submit this same package to SUSE for SLE, it complains:
[ 117s] libopeniscsiusr0_2_0.x86_64: E: shlib-policy-name-error (Badness: 10000) libopeniscsiusr0 [ 117s] Your package contains a single shared library but is not named after its [ 117s] SONAME.
So it _looks_ like it's suggesting the package be named "libopeniscsiusr0"? But the "libopeniscsiusr0" file is just a symlink. By the way, my package has been like this for a couple of year in SLE, so I'm not sure why it's complaining. Help? -- Lee Duncan