Details

    • Technical task
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 10.7, 10.8, 10.9
    • 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

          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.