Results 1 to 7 of 7

Thread: Should I name this package vkbasalt-devel to fix E: shlib-policy-name-error?

  1. #1
    Join Date
    Oct 2018
    Location
    Atlantis
    Posts
    179

    Default Should I name this package vkbasalt-devel to fix E: shlib-policy-name-error?

    Hello,
    I am packaging vkbasalt.
    https://build.opensuse.org/package/s...great/vkbasalt

    The problem is that it produce a file that is %{_libdir}/libvkbasalt.so
    RPMLINT error is

    Code:
    vkbasalt.x86_64: E: shlib-policy-name-error (Badness: 10000) libvkbasalt
    Your package contains a single shared library but is not named after its
    SONAME.
    Which I think RPMLINT told me to rename the package to libvkbasalt.
    But I was told that it should remain as vkbasalt.
    https://build.opensuse.org/request/show/834343#comments-list

    Should I split it into devel package? However, I do not think that it is devel package, so what should I do?

    Thank you.

  2. #2
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    29,680
    Blog Entries
    15

    Default Re: Should I name this package vkbasalt-devel to fix E: shlib-policy-name-error?

    Quote Originally Posted by andythe_great View Post
    Hello,
    I am packaging vkbasalt.
    https://build.opensuse.org/package/s...great/vkbasalt

    The problem is that it produce a file that is %{_libdir}/libvkbasalt.so
    RPMLINT error is

    Code:
    vkbasalt.x86_64: E: shlib-policy-name-error (Badness: 10000) libvkbasalt
    Your package contains a single shared library but is not named after its
    SONAME.
    Which I think RPMLINT told me to rename the package to libvkbasalt.
    But I was told that it should remain as vkbasalt.
    https://build.opensuse.org/request/show/834343#comments-list

    Should I split it into devel package? However, I do not think that it is devel package, so what should I do?

    Thank you.
    Hi
    Yes, split out the shared library into libvkbasalt<soname>, you can find the soname (I normally just pop into the build root to run this);

    Code:
    readelf -a <lib_name>.so | grep SONAME
    Just create a define in your spec file, then use %{lib_name};

    Code:
    %define lib_name libvkbasalt<soname>
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    SUSE SLE, openSUSE Leap/Tumbleweed (x86_64) | GNOME DE
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!

  3. #3
    Join Date
    Oct 2018
    Location
    Atlantis
    Posts
    179

    Default Re: Should I name this package vkbasalt-devel to fix E: shlib-policy-name-error?

    Quote Originally Posted by malcolmlewis View Post
    Hi
    Yes, split out the shared library into libvkbasalt<soname>, you can find the soname (I normally just pop into the build root to run this);

    Code:
    readelf -a <lib_name>.so | grep SONAME
    Just create a define in your spec file, then use %{lib_name};

    Code:
    %define lib_name libvkbasalt<soname>
    Hi,

    I have split the package into libvkbasalt and vkbasalt.
    Do you think vkbasalt should depend on libvkbasalt or vice versa?

  4. #4
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    29,680
    Blog Entries
    15

    Default Re: Should I name this package vkbasalt-devel to fix E: shlib-policy-name-error?

    Quote Originally Posted by andythe_great View Post
    Hi,

    I have split the package into libvkbasalt and vkbasalt.
    Do you think vkbasalt should depend on libvkbasalt or vice versa?
    Hi
    Check the build log at the end to see if it detects (It should), then let rpm sort it out. You can also check the details tab for each of those two rpms.
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    SUSE SLE, openSUSE Leap/Tumbleweed (x86_64) | GNOME DE
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!

  5. #5
    Join Date
    Oct 2018
    Location
    Atlantis
    Posts
    179

    Default Re: Should I name this package vkbasalt-devel to fix E: shlib-policy-name-error?

    Quote Originally Posted by malcolmlewis View Post
    Hi
    Check the build log at the end to see if it detects (It should), then let rpm sort it out. You can also check the details tab for each of those two rpms.
    It does not detect each other.

    My file list look like this.

    Code:
    %files -n %{libname}
    %{_libdir}/libvkbasalt.so
    
    %files
    %license LICENSE
    %doc README.md
    %dir %{_datadir}/vulkan
    %dir %{_datadir}/vulkan/implicit_layer.d
    %{_datadir}/vulkan/implicit_layer.d/vkBasalt.json
    But I don't feel like it make sense... If it is like this, vkbasalt only have .json file. So I think I have to make vkbasalt depend on libvkbasalt.

  6. #6
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    29,680
    Blog Entries
    15

    Default Re: Should I name this package vkbasalt-devel to fix E: shlib-policy-name-error?

    Quote Originally Posted by andythe_great View Post
    It does not detect each other.

    My file list look like this.

    Code:
    %files -n %{libname}
    %{_libdir}/libvkbasalt.so
    
    %files
    %license LICENSE
    %doc README.md
    %dir %{_datadir}/vulkan
    %dir %{_datadir}/vulkan/implicit_layer.d
    %{_datadir}/vulkan/implicit_layer.d/vkBasalt.json
    But I don't feel like it make sense... If it is like this, vkbasalt only have .json file. So I think I have to make vkbasalt depend on libvkbasalt.
    Hi
    Yes, but shouldn't it need vulkan as a requires as well? Isn't the vkBasalt.conf file missing?
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    SUSE SLE, openSUSE Leap/Tumbleweed (x86_64) | GNOME DE
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!

  7. #7
    Join Date
    Oct 2018
    Location
    Atlantis
    Posts
    179

    Default Re: Should I name this package vkbasalt-devel to fix E: shlib-policy-name-error?

    Quote Originally Posted by malcolmlewis View Post
    Hi
    Yes, but shouldn't it need vulkan as a requires as well? Isn't the vkBasalt.conf file missing?
    SOLVED

    I have submit this to graphics repo. RPMLINT warning is actually false positive. I have to add rpmlintrc to it
    To quote the graphics maintainer.

    Code:
    The name does not fit. 'libvkbasalt.so' is not a generic shared library, but a module loaded by the vulkan runtime library.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •