Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-27033 Start using pure mariadb in DEB file name and remove version information from name
  3. MDEV-28120

Provider plugins packages are not passing Lintian

Details

    • Technical task
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 10.7(EOL), 10.8(EOL), 10.9(EOL)
    • 10.7.4, 10.8.3
    • Packaging
    • None

    Description

      Provider Plugins throws Lintian False-Positive Errors. This because these shared objects does not share any symbols from Glibc and Lintian uses command objdump -X to check exactly which symbols are required by shared object. As Lintian error itself if correct it's not error and it's false-positive which should be overrided with .lintian-overrides -files

      • E: mariadb-plugin-provider-bzip2: library-not-linked-against-libc usr/lib/mysql/plugin/provider_bzip2.so
      • E: mariadb-plugin-provider-lz4: library-not-linked-against-libc usr/lib/mysql/plugin/provider_lz4.so
      • E: mariadb-plugin-provider-lzma: library-not-linked-against-libc usr/lib/mysql/plugin/provider_lzma.so
      • E: mariadb-plugin-provider-lzo: library-not-linked-against-libc usr/lib/mysql/plugin/provider_lzo.so
      • E: mariadb-plugin-provider-snappy: library-not-linked-against-libc usr/lib/mysql/plugin/provider_snappy.so

      Which should be suppressed also there is problem in debian/control file

      • E: mariadb-plugin-provider-bzip2: extended-description-is-empty
      • E: mariadb-plugin-provider-lz4: extended-description-is-empty
      • E: mariadb-plugin-provider-lzma: extended-description-is-empty
      • E: mariadb-plugin-provider-lzo: extended-description-is-empty
      • E: mariadb-plugin-provider-snappy: extended-description-is-empty

      Debian Policy Manual section 3.4 says that they are needed

      Attachments

        Activity

          Ascending order - Click to sort in descending order
          illuusio Tuukka Pasanen added a comment -

          There is clean Lintian runs:
          https://salsa.debian.org/illuusio/mariadb-server/-/jobs/2581906

          illuusio Tuukka Pasanen added a comment - There is clean Lintian runs: https://salsa.debian.org/illuusio/mariadb-server/-/jobs/2581906
          serg Sergei Golubchik added a comment -

          https://lintian.debian.org/tags/library-not-linked-against-libc

          It is theoretically possible to have a library which doesn't use any symbols from libc, but it is far more likely that this is a violation of the requirement that "shared libraries must be linked against all libraries that they use symbols from in the same way that binaries are".

          in this case those provider plugins, exactly, don't use any symbols from libc, as they don't do anything besides a couple of assignments. So, it's a false positive.

          serg Sergei Golubchik added a comment - https://lintian.debian.org/tags/library-not-linked-against-libc It is theoretically possible to have a library which doesn't use any symbols from libc, but it is far more likely that this is a violation of the requirement that "shared libraries must be linked against all libraries that they use symbols from in the same way that binaries are". in this case those provider plugins, exactly , don't use any symbols from libc, as they don't do anything besides a couple of assignments. So, it's a false positive.
          illuusio Tuukka Pasanen added a comment -

          Yes and it's more objdump problem as it just deals with current binary. If you ldd those shared object it reports correctly that they links against libc.

          illuusio Tuukka Pasanen added a comment - Yes and it's more objdump problem as it just deals with current binary. If you ldd those shared object it reports correctly that they links against libc.

          People

            otto Otto Kekäläinen
            illuusio Tuukka Pasanen
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Git Integration

                Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.