Temporarily get Salsa-CI pass and not stall work with broken pipeline
and instead be green for now and raise alerts only if new Lintian errors
are introduced.

The author Vicențiu Ciorbaru confirmed this patch can be dropped as it
has already been applied upstream.

The author Jan Wagner confirmed the patches can be dropped as they are no
longer relevant with systemd. From now on the correct approach would be
to follow the method described in the MariaDB knowledgebase:
https://mariadb.com/kb/en/library/systemd/#interacting-with-multiple-mariadb-server-processes

Update libmariadb-dev.links to restore /usr/include/mysql compatibility symlinks lost when the default switched from 10.1 to 10.3 (Closes: #917266)

Lintian discovered an unused override entry in its database. Most likely
it was used for a false-positive that has been fixed. However, some tags
are only triggered in packages built on certain architectures. In this
case, the override may need an architecture qualifier.

This mimics how libmariadbclient-dev used to breaks/replaces the same
libmysqlclient-dev package. These packages are not supposed to be
co-installable anyway.

Among others, the following files conflict:
- /usr/bin/mysql_config
- libmysqlservices.a
- mysql.m4

Also, wrap-and-sort -a in this commit.

The package contains only one single file that should not overlap with
anything that already exists (/usr/lib/*/libmariadbd.so.19).

The author James Cowgill confirmed the patch can be dropped due
to the issue being fixed by upstream by now.

Source: https://github.com/facebook/rocksdb/commit/ca32fc17184e4b7b2942105067f4038191a7c4d6.patch

See https://github.com/MariaDB/server/commit/1a4248ad6c867096ac46ac11ca60f7fb5b12d5bd

See also https://jira.mariadb.org/browse/MDEV-14918

Lintian detects the command-with-path-in-maintainer-script on line 143
from the postinst script while it was previously on line 140. So this
override was no more working.

When upgrading from a system with libmariadbclient18 installed, this
conflict line forces libmariadbclient18 to be uninstalled when in fact
it should only be upgraded.

The line was imported from upstream sources where their origin in a bit
unclear and probably don't have any function in Debian official.

Anything that builds against libmariadb-dev expects to have libssl-dev
also available because libmariadb3 has these compilation flags:

pkg-config --libs libmariadb
-L/usr/lib/x86_64-linux-gnu/ -lmariadb -lz -ldl -lm -lpthread -lssl -lcrypto

Vicențiu Ciorbaru authored Dec 20, 2018 and Otto Kekäläinen committed Dec 20, 2018

The current testcase was inserting the same value in a SERIAL column,
which is an ALIAS for BIGINT UNSIGNED NOT NULL AUTO_INCREMENT UNIQUE.
Duplicate values are not allowed.

The author Samuel Thibault confirmed the patch can be dropped due
to the issue being fixed by upstream by now.

See https://salsa.debian.org/salsa-ci-team/dummypackage/tree/master/debian

This is needed to get the Gitlab pipeline passing again. Without this
it will fail with error message:
  /usr/bin/chown: invalid user: 'salsa-ci:0'

The entire source package has Priority: optional so it is useless for
any package to redefine that.

TokuDB will fail it this library is missing and stop the entire server
from starting.

This option to mysql_install_db no longer works on MariaDB 10.3 so it
has to be removed for the postinstall script to complete successfully.