Start using pure mariadb in DEB file name and remove version information from name (MDEV-27033)

[MDEV-28120] Provider plugins packages are not passing Lintian Created: 2022-03-18  Updated: 2022-03-23  Resolved: 2022-03-23

Status: Closed
Project: MariaDB Server
Component/s: Packaging
Affects Version/s: 10.7, 10.8, 10.9
Fix Version/s: 10.7.4, 10.8.3

Type: Technical task Priority: Major
Reporter: Tuukka Pasanen Assignee: Otto Kekäläinen
Resolution: Fixed Votes: 0
Labels: 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

 Comments   
Comment by Tuukka Pasanen [ 2022-03-18 ]

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

Comment by Sergei Golubchik [ 2022-03-18 ]

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.

Comment by Tuukka Pasanen [ 2022-03-21 ]

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.

Generated at Thu Feb 08 09:58:13 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.