Package: mariadb / 1:11.4.4-2
Metadata
Package | Version | Patches format |
---|---|---|
mariadb | 1:11.4.4-2 | 3.0 (quilt) |
Patch series
view the series filePatch | File delta | Description |
---|---|---|
0025 Change the default optimization from O3 to O2 in mys.patch | (download) |
cmake/build_configurations/mysql_release.cmake |
12 6 6 - 0 ! |
change the default optimization from -o3 to -o2 in mysql_release.cmake BUILD_CONFIG profile |
rocksdb kfreebsd.patch | (download) |
storage/rocksdb/build_rocksdb.cmake |
2 2 0 - 0 ! |
rocksdb-kfreebsd Upstream has merged this but we still need to wait for it to be included in a RocksDB release and imported into MariaDB and then into Debian. Bug: https://jira.mariadb.org/browse/MDEV-19251 |
env perl usr bin perl.patch | (download) |
mysql-test/lib/process-purecov-annotations.pl |
2 1 1 - 0 ! |
fix perl path in scripts Fix Lintian issue https://lintian.debian.org/tags/incorrect-path-for-interpreter.html Upstream will never accept this patch, see https://github.com/MariaDB/server/pull/1718 |
fix spelling rocksdb.patch | (download) |
storage/rocksdb/rocksdb/db/external_sst_file_ingestion_job.cc |
4 2 2 - 0 ! |
fix various spelling errors still found in code Two upstream PRs remain that have been merged, but not imported on MariaDB yet. |
fix reproducible builds rocksdb.patch | (download) |
storage/rocksdb/rocksdb/util/build_version.cc.in |
6 3 3 - 0 ! |
make rocksdb build reproducible The RocksDB binary included a string with the build timestamp: > rocksdb_build_git_date:@2021-05-23-16:04:38@ As this changes from build to build, it makes the builds unreproducible. Simply removing it solves the issue. This temporary fix can be removed when a proper fix already done in upstream lands in MariaDB when the RocksDB submodule is updated to a newer release. |
mroonga mrn lib dirs path reproducible build.patch | (download) |
storage/mroonga/CMakeLists.txt |
12 4 8 - 0 ! |
cmake: add support for reproducible builds We should use relative path not absolute path. We can use target without breaking reproducibility. |
install files into usr.patch | (download) |
cmake/install_layout.cmake |
4 2 2 - 0 ! |
[patch] install pam modules and systemd units into /usr Since Debian trixie all files need to be installed into their canonical location under /usr. |
1006531 hurd no auth socket.patch | (download) |
cmake/build_configurations/mysql_release.cmake |
5 4 1 - 0 ! |
mariadb: ftbfs on hurd-i386: undefined reference to misc functions and files requires https://github.com/MariaDB/server/pull/2893 as debian explicit architectures aren't needed since dh_auto_configure handles this. If it works, upstream welcome. Hurd string from uname -m, "SYSTEM processor: i686-AT386" in mariadb output. And wiki reference https://en.wikipedia.org/wiki/Uname |
startup message.patch | (download) |
client/mysql.cc |
3 3 0 - 0 ! |
show banner in server and client startup to drive community engagement Suggest to users that they can support MariaDB development by simply giving a star on GitHub. This patch experiments with how well such a banner works, and may later change the contents to drive some other kind of engagement. Client output: Welcome to the MariaDB monitor. Commands end with ; or \g. Your MariaDB connection id is 34 Server version: 10.11.7-MariaDB-3 Debian n/a Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others. Support MariaDB developers by giving a star at https://github.com/MariaDB/server Type 'help;' or '\h' for help. Type '\c' to clear the current input statement. MariaDB [(none)]> Server output: [Note] Support MariaDB developers by giving a star at https://github.com/MariaDB/server Server output if build in git directory: [Note] Starting MariaDB 10.11.7-MariaDB-3 source revision 219efb0a6ab0ee8ce2ec831c715783586c4db2ef as process 5426 |
fix spelling mariadb.patch | (download) |
extra/mariabackup/innobackupex.cc |
4 2 2 - 0 ! |
fix misc spelling in mariadb server repository |
hurd i386 plugin_disks_information_schema_disks.cc.patch | (download) |
plugin/disks/information_schema_disks.cc |
3 3 0 - 0 ! |
bug#1069094: mariadb: ftbfs on hurd-i386 Define PATH_MAX if not defined. |
hurd i386 storage_connect_ioapi.h.patch | (download) |
storage/connect/ioapi.h |
5 3 2 - 0 ! |
bug#1069094: mariadb: ftbfs on hurd-i386 Add Hurd to define __USE_FILE_OFFSET64 et al. |
hide mysql command deprecation warnings.patch | (download) |
mysys/my_init.c |
3 2 1 - 0 ! |
disable the 'mysql*' command deprecation warning Many command-line tools expect the commands they run to return without any output in stderr or having error codes. The fact that now in MariaDB 11.4 all 'mysql*' commands emit a deprecation warning causes a lot of scripts to fail, such as the /etc/init.d/mariadb itself and many dependent programs as witnessed via Debian autopkgtests. See examples below. https://ci.debian.net/packages/m/mariadb-connector-odbc/testing/amd64/48373500/ https://ci.debian.net/packages/p/pam-mysql/testing/amd64/48373511/ https://ci.debian.net/packages/r/roundcube/testing/amd64/48373518/ |
1063738 x32 compile time assert.patch | (download) |
tests/mysql_client_fw.c |
2 1 1 - 0 ! |
make compile_time_assert compatible with x32 (closes: #1063738) The x32 build was failing on: compile_time_assert(sizeof(MYSQL) == 77*sizeof(void*) 656); Reported upstream at https://jira.mariadb.org/browse/MDEV-34195. This is a regression from upstream commits c432c9ef and 06a884a57071. Fix is based on advice from https://lists.debian.org/debian-amd64/2024/07/msg00003.html which is also aligned with https://wiki.debian.org/X32Port. |
Fix spelling of of allows one to.patch | (download) |
mysql-test/main/mysqld--help.result |
15 8 7 - 0 ! |
fix spelling of 'allows one to' Fix the following Lintian nags introduced in commit c8d040938a7ebe10e62506a726702c5990ef4dda: I: mariadb-backup: spelling-error-in-binary "allows to" "allows one to" [usr/bin/mariadb-backup] I: mariadb-server-core: spelling-error-in-binary "allows to" "allows one to" [usr/sbin/mariadbd] I: mariadb-test: spelling-error-in-binary "allows to" "allows one to" [usr/bin/mariadb-client-test-embedded] I: mariadb-test: spelling-error-in-binary "allows to" "allows one to" [usr/bin/mariadb-test-embedded] I: mariadb-test: spelling-error-in-binary "allows to" "allows one to" [usr/bin/test-connect-t] |
MDEV 35528 mariadb binlog cannot process more than 1 logf.patch | (download) |
client/mysqlbinlog.cc |
2 0 2 - 0 ! |
mdev-35528: mariadb-binlog cannot process more than 1 logfiles when --stop-datetime is specified Fix regression introduced by commits 9588526 and 242b67f which attempted to address MDEV-27037. With the regression, mariadb-binlog cannot process multiple log files when --stop-datetime is specified. Remove the code to set retval as OK_STOP if mariadb-binlog finished processing current log file but not reached specified --stop-datetime or --stop-position, to make it possible to continue process following log files. All new code of the whole pull request, including one or several files that are either new files or modified ones, are contributed under the BSD-new license. I am contributing on behalf of my employer Amazon Web Services, Inc. |