| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| 1063738-x32-compile-time-assert.patch | 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. |
Otto Kekalainen <otto@debian.org> | no | 2024-07-04 | ||
| Fix-spelling-of-of-allows-one-to.patch | Fix spelling of 'allows one to' Fix the following Lintian nags introduced in commit c8d040938a7ebe10e62506a726702c5990ef4dda: |
=?utf-8?b?T3R0byBLZWvDpGzDpGluZW4=?= <otto@debian.org> | no | 2024-11-04 | ||
| MDEV-35528-mariadb-binlog-cannot-process-more-than-1-logf.patch | 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. |
Xiaochuan Cui <xiaochuc@amazon.com> | yes | https://patch-diff.githubusercontent.com/raw/MariaDB/server/pull/3670.patch | 2024-11-29 | |
| 0025-Change-the-default-optimization-from-O3-to-O2-in-mys.patch | Change the default optimization from -O3 to -O2 in mysql_release.cmake BUILD_CONFIG profile | Ondrej Sury <ondrej@debian.org> | no | upstream | 2017-11-22 | |
| rocksdb-kfreebsd.patch | 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. # Merged in RocksDB 6.12.6 but not updated into MariaDB yet |
Andrew Kryczka <andrewkr@fb.com> | yes | upstream | 2020-06-16 | |
| env-perl-usr-bin-perl.patch | 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 |
Otto Kekalainen <otto@debian.org> | yes | https://patch-diff.githubusercontent.com/raw/MariaDB/server/pull/1718.patch | 2020-12-20 | |
| fix-spelling-rocksdb.patch | Fix various spelling errors still found in code Two upstream PRs remain that have been merged, but not imported on MariaDB yet. # Merged in RocksDB 7.3.1, but not updated into MariaDB yet |
Otto Kekalainen <otto@debian.org> | yes | https://patch-diff.githubusercontent.com/raw/facebook/rocksdb/pull/9653.patch | 2022-03-02 | |
| fix-reproducible-builds-rocksdb.patch | 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. # Merged in RocksDB 6.19.3, but not updated into MariaDB yet |
Otto Kekalainen <otto@debian.org> | yes | upstream | https://github.com/facebook/rocksdb/commit/0a9a05ae12943b1529ef1eabbca5ce5a71c986bf | 2021-06-29 |
| mroonga-mrn-lib-dirs-path-reproducible-build.patch | cmake: add support for reproducible buildS We should use relative path not absolute path. We can use target without breaking reproducibility. |
Sutou Kouhei <kou@clear-code.com> | not-needed | upstream | https://github.com/mroonga/mroonga/issues/298#issuecomment-1030815927 | 2022-02-05 |
| install-files-into-usr.patch | [PATCH] Install PAM modules and systemd units into /usr Since Debian trixie all files need to be installed into their canonical location under /usr. |
Michael Biebl <biebl@debian.org> | no | https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061348 | 2024-01-22 | |
| 1006531-hurd-no-auth-socket.patch | 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 |
Daniel Black <daniel@mariadb.org> | no | https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006531 | 2024-01-28 | |
| startup-message.patch | 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 |
Otto Kekalainen <otto@debian.org> | no | 2024-03-10 | ||
| fix-spelling-mariadb.patch | Fix misc spelling in MariaDB Server repository | Otto Kekalainen <otto@debian.org> | no | 2024-03-10 | ||
| hurd-i386-plugin_disks_information_schema_disks.cc.patch | Bug#1069094: mariadb: FTBFS on hurd-i386 Define PATH_MAX if not defined. |
Svante Signell <svante.signell@gmail.com> | no | https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069094 | 2024-04-20 | |
| hurd-i386-storage_connect_ioapi.h.patch | Bug#1069094: mariadb: FTBFS on hurd-i386 Add Hurd to define __USE_FILE_OFFSET64 et al. |
Svante Signell <svante.signell@gmail.com> | no | https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069094 | 2024-04-20 | |
| hide-mysql-command-deprecation-warnings.patch | 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/ |
Otto Kekalainen <otto@debian.org> | no | 2024-06-30 |