February 2018 - discuss - lists.mariadb.org

[Maria-discuss] Galera 23.2.7 mariadb 5.5.33a msvc 1600 binaries available
by Yann Nayn 18 Nov '24

18 Nov '24

Binaries have been uploaded for both x86 and amd64 platforms. due to github file size limitations , the directories have been uploaded unarchived. for Win33 binaries , please checkout https://github.com/YannNayn/galera-mariadb-win32.git and for Win64(amd64) binaries (being uploaded/pushed): https://github.com/YannNayn/galera-mariadb-win64.git they are not recommended for a production environment. in the my.cnf file: _________ wsrep_provider=galera_smm.dll wsrep_sst_method=msqldump # percona xtrabackup will be tested soon _________ libevent and openssl(the provided binaries use respectively 2.1.3-alpha and 1.1.0-dev versions ) will be added next on github some limitations are stated on openssl website copied here for convenience: ____________ from http://www.openssl.org/ ____________ This software package uses strong cryptography, so even if it is created, maintained and distributed from liberal countries in Europe (where it is legal to do this), it falls under certain export/import and/or use restrictions in some other parts of the world. PLEASE REMEMBER THAT EXPORT/IMPORT AND/OR USE OF STRONG CRYPTOGRAPHY SOFTWARE, PROVIDING CRYPTOGRAPHY HOOKS OR EVEN JUST COMMUNICATING TECHNICAL DETAILS ABOUT CRYPTOGRAPHY SOFTWARE IS ILLEGAL IN SOME PARTS OF THE WORLD. SO, WHEN YOU IMPORT THIS PACKAGE TO YOUR COUNTRY, RE-DISTRIBUTE IT FROM THERE OR EVEN JUST EMAIL TECHNICAL SUGGESTIONS OR EVEN SOURCE PATCHES TO THE AUTHOR OR OTHER PEOPLE YOU ARE STRONGLY ADVISED TO PAY CLOSE ATTENTION TO ANY EXPORT/IMPORT AND/OR USE LAWS WHICH APPLY TO YOU. THE AUTHORS OF OPENSSL ARE NOT LIABLE FOR ANY VIOLATIONS YOU MAKE HERE. SO BE CAREFUL, IT IS YOUR RESPONSIBILITY. ________________________________________________ msvc 1600 redistributables SP1 need to be installed/available on the target machine: vcredist_x86.exe : http://www.microsoft.com/en-us/download/details.aspx?id=8328 vcredist_x64.exe : http://www.microsoft.com/en-us/download/details.aspx?id=13523 MSys binaries are provided and msqld.bat should then be used instead of mysqld.exe (e.g. mysld.bat --console --wsrep_cluster_address=gcomm:// ) in order to have a working sh shell(cygwin has been proved to do it as well) Please note that oqgraph is disabled (boost trunk is used , that is 1.55) Comments and suggestions are welcome.

2 1

[Maria-discuss] why stdout? -> [Note] /usr/libexec/mysqld (mysqld 10.0.20-MariaDB) starting as process 115096
by Reindl Harald 05 Jul '20

05 Jul '20

Aug 6 12:24:24 testserver mysqld: 150806 12:24:24 [Note] /usr/libexec/mysqld (mysqld 10.0.20-MariaDB) starting as process 115096 ... why is this now stdout instead mysql logs? on systemd based distributions that spits now to the global syslog and finally on machines restarting 2 instances every hour for backup reasons it annoys until 10.0.19 or 10.0.20 that was not this way

5 13

[Maria-discuss] MariaDB-10.2.11 Long Time To Start
by Michael Caplan 15 Mar '19

15 Mar '19

Hi, I'm setting up a replication slave based off of MySQL 5.6. There are a large number of tables (400K). The MySQL 5.6 master takes around 10 minutes to start up, where the new MariaDB 10.2 slave takes close to 30 minutes. What is making the startup take soo long? In the below mysql log, you can see in the startup sequence between "Highest supported file format is Barracuda." and "InnoDB: 128 out of 128 rollback segments are active." the startup process takes the majority of its time: 2018-01-07 9:38:15 139980432365760 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2018-01-07 9:38:15 139980432365760 [Note] InnoDB: Uses event mutexes 2018-01-07 9:38:15 139980432365760 [Note] InnoDB: Compressed tables use zlib 1.2.8 2018-01-07 9:38:15 139980432365760 [Note] InnoDB: Using Linux native AIO 2018-01-07 9:38:15 139980432365760 [Note] InnoDB: Number of pools: 1 2018-01-07 9:38:15 139980432365760 [Note] InnoDB: Using SSE2 crc32 instructions 2018-01-07 9:38:15 139980432365760 [Note] InnoDB: Initializing buffer pool, total size = 54G, instances = 8, chunk size = 128M 2018-01-07 9:38:18 139980432365760 [Note] InnoDB: Completed initialization of buffer pool 2018-01-07 9:38:18 139918113195776 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority(). 2018-01-07 9:38:18 139980432365760 [Note] InnoDB: Highest supported file format is Barracuda. 2018-01-07 10:11:48 139980432365760 [Note] InnoDB: 128 out of 128 rollback segments are active. 2018-01-07 10:11:48 139980432365760 [Note] InnoDB: Creating shared tablespace for temporary tables 2018-01-07 10:11:48 139980432365760 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ... 2018-01-07 10:11:48 139980432365760 [Note] InnoDB: File './ibtmp1' size is now 12 MB. 2018-01-07 10:11:48 139980432365760 [Note] InnoDB: Waiting for purge to start 2018-01-07 10:11:48 139980432365760 [Note] InnoDB: 5.7.20 started; log sequence number 1394303471760 2018-01-07 10:11:48 139919461500672 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool 2018-01-07 10:11:48 139980432365760 [Note] Server socket created on IP: '::'. 2018-01-07 10:11:49 139980432365760 [Note] Reading of all Master_info entries succeded 2018-01-07 10:11:49 139980432365760 [Note] Added new Master_info '' to hash table 2018-01-07 10:11:49 139980432365760 [Note] /usr/sbin/mysqld: ready for connections. Version: '10.2.11-MariaDB-10.2.11+maria~xenial-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 mariadb.org binary distribution Any ideas why? I've included my my.conf file below. Thanks, Mike # Generated by Percona Configuration Wizard (http://tools.percona.com/) version REL5-20120208 # Configuration name usaddxprdsqlpm3 generated formcaplan(a)labnet.net at 2017-12-22 13:49:58 [mysql] # CLIENT # port = 3306 socket = /var/lib/mysql/mysql.sock [mysqladmin] # CLIENT # port = 3306 socket = /var/lib/mysql/mysql.sock [mysqld] # GENERAL # user = mysql default-storage-engine = InnoDB socket = /var/lib/mysql/mysql.sock pid-file = /var/lib/mysql/mysql.pid character-set-server = utf8 collation_server = utf8_general_ci performance_schema = 0 # MyISAM # key-buffer-size = 32M myisam-recover = FORCE,BACKUP # SAFETY # max-allowed-packet = 20M max-connect-errors = 1000000 skip-name-resolve sysdate-is-now = 1 innodb = FORCE # DATA STORAGE # datadir = /var/lib/mysql/ # BINARY LOGGING # log-bin = /var/lib/mysql/mysql-bin binlog_format = MIXED server-id = 3 expire-logs-days = 7 sync-binlog = 1 # REPLICATION # read-only = 1 skip-slave-start = 1 log-slave-updates = 1 relay-log = /var/lib/mysql/relay-bin slave-net-timeout = 60 sync-master-info = 1 sync-relay-log = 1 sync-relay-log-info = 1 # CACHES AND LIMITS # tmp-table-size = 32M max-heap-table-size = 32M query-cache-type = 0 query-cache-size = 0 max-connections = 500 thread-cache-size = 50 open-files-limit = 65535 table-definition-cache = 4096 table-open-cache = 10240 # INNODB # innodb-flush-method = O_DIRECT innodb-log-files-in-group = 2 innodb-log-file-size = 512M innodb-flush-log-at-trx-commit = 1 innodb-file-per-table = 1 innodb-buffer-pool-size = 54G # LOGGING # log-error = /var/lib/mysql/mysql-error.log log-queries-not-using-indexes = 0 slow-query-log = 0 slow-query-log-file = /var/lib/mysql/mysql-slow.log [mariadb] plugin-load-add=file_key_management file_key_management_filename=/var/lib/mysql/keys.enc file_key_management_filekey=FILE:/var/lib/mysql/mysql.key file_key_management_encryption_algorithm=AES_CTR encrypt_binlog=0

3 19

[Maria-discuss] Charsets and collations
by Peter Laursen 20 Apr '18

20 Apr '18

Does anybody know if there are any plans to bring collations added in MySQL 8 - refer http://mysqlserverteam.com/new-collations-in-mysql-8-0-0/ - to MariaDB and are there any plans to change the default charset to a unicode-based one? -- Peter -- Webyog

2 2

[Maria-discuss] Backing up a single database with mariabackup?
by Kevin Poitra 01 Mar '18

01 Mar '18

I've been working on redoing our database backup routines, and have looked into mariabackup as mysqldump doesn't cut it anymore given the size of our schemas. We have multiple schemas that need to be backed up - they all vary in size, and they also vary in backup frequency (some need to be backed up on a six hour period, others can go a day in between backups). On top of that, our database consists of two database servers, running in a master-slave configuration. To start, I ran this command against one of our schemas: mariabackup --backup --user root --password <pass> --databases db1 That generated a copy of the 'db1' schema's data files, along with some files used by MariaDB itself (aria_log, ib_buffer_pool, ib_logfile, ibdata, so on). This works perfectly - we can create separate backups of each of our schemas. Restoring seems to be another story however. After '--prepare'ing the backup and issuing the mariabackup --copy-back command, it complains that the data directory must be empty. If I have separated backups, would it be possible for me to restore those schemas under one database (or rather, one MariaDB instance)? To be even clearer, if I've made backups of schemas 'db1', 'db2', and 'db3', I don't seem to be able to restore them all under the same database instance - is there something I'm not understanding?

2 1

[Maria-discuss] procedure to change database encryption with file_key_management plugin?
by obsa＠mm.st 27 Feb '18

27 Feb '18

I've built mysqld -V mysqld Ver 10.2.14-MariaDB-log for Linux on x86_64 (Source distribution) I'm setting up encryption, following https://mariadb.com/kb/en/library/encryption/ https://mariadb.com/kb/en/library/data-at-rest-encryption/ I created my key file openssl rand -hex 32 b650adbc0c5df1bc3e766b4b65f26dc76c76ed81b955bbedaf50e1d4e16fc732 /etc/mariadb/keys.txt 1;b650adbc0c5df1bc3e766b4b65f26dc76c76ed81b955bbedaf50e1d4e16fc732 encrypted it openssl enc -aes-256-cbc -k 'test_passphrase' -md sha1 -in /etc/mariadb/keys.txt -out /etc/mariadb/keys.enc verified it openssl aes-256-cbc -d -md sha1 -k 'test_passphrase' -in /etc/mariadb/keys.enc 1;b650adbc0c5df1bc3e766b4b65f26dc76c76ed81b955bbedaf50e1d4e16fc732 I've enabled "everything" encryption using that keyfile [mysqld] plugin_dir=/opt/mariadb/lib/plugin plugin-load-add=file_key_management file-key-management file_key_management_encryption_algorithm=aes_ctr file_key_management_filekey = 'test_filekey' file_key_management_filename = /etc/mariadb/enc/keys.enc aria-encrypt-tables = 1 encrypt-binlog = 1 encrypt-tmp-disk-tables = 1 encrypt-tmp-files = 1 innodb_default_encryption_key_id = 1 innodb-encrypt-log = off innodb-encrypt-tables = on innodb-encryption-threads = 4 innodb-tablespaces-encryption = 1 verified the plugin loads mysql -e "show plugins;" | grep ENC INNODB_TABLESPACES_ENCRYPTION ACTIVE INFORMATION SCHEMA NULL BSD file_key_management ACTIVE ENCRYPTION file_key_management.so GPL on startup it looks like it starts up ok 2018-02-21 13:01:29 139729003899072 [Note] InnoDB: 5.7.21 started; log sequence number 7206290786 2018-02-21 13:01:29 139729003899072 [Note] InnoDB: Creating #1 encryption thread id 139727810316032 total threads 4. 2018-02-21 13:01:29 139729003899072 [Note] InnoDB: Creating #2 encryption thread id 139727801923328 total threads 4. 2018-02-21 13:01:29 139727818708736 [Note] InnoDB: Loading buffer pool(s) from /home/data/db/ib_buffer_pool 2018-02-21 13:01:29 139729003899072 [Note] InnoDB: Creating #3 encryption thread id 139727793530624 total threads 4. 2018-02-21 13:01:29 139729003899072 [Note] InnoDB: Creating #4 encryption thread id 139727785137920 total threads 4. 2018-02-21 13:01:29 139727818708736 [Note] InnoDB: Buffer pool(s) load completed at 180222 13:01:29 2018-02-21 13:01:29 139729003899072 [Note] Using encryption key id 1 for temporary files 2018-02-21 13:01:29 139729003899072 [Note] Server socket created on IP: '127.0.0.1'. 2018-02-21 13:01:29 139729003899072 [Note] Reading of all Master_info entries succeded 2018-02-21 13:01:29 139729003899072 [Note] Added new Master_info '' to hash table 2018-02-21 13:01:29 139729003899072 [Note] /opt/mariadb/bin/mysqld: ready for connections. Version: '10.2.14-MariaDB-log' socket: '/var/cache/mariadb/mariadb.sock' port: 3306 Source distribution and verified table encryption mysql -e "SELECT * FROM INFORMATION_SCHEMA.INNODB_TABLESPACES_ENCRYPTION;" +-------+-------------------------------------------+-------------------+--------------------+-----------------+---------------------+--------------------------+------------------------------+----------------+----------------------+ | SPACE | NAME | ENCRYPTION_SCHEME | KEYSERVER_REQUESTS | MIN_KEY_VERSION | CURRENT_KEY_VERSION | KEY_ROTATION_PAGE_NUMBER | KEY_ROTATION_MAX_PAGE_NUMBER | CURRENT_KEY_ID | ROTATING_OR_FLUSHING | +-------+-------------------------------------------+-------------------+--------------------+-----------------+---------------------+--------------------------+------------------------------+----------------+----------------------+ | 1375 | mysql/gtid_slave_pos | 1 | 1 | 1 | 1 | NULL | NULL | 1 | 0 | | 1465 | mysql/innodb_index_stats | 1 | 1 | 1 | 1 | NULL | NULL | 1 | 0 | | 1466 | mysql/innodb_table_stats | 1 | 1 | 1 | 1 | NULL | NULL | 1 | 0 | | 18999 | testdata/table0001 | 1 | 0 | 1 | 1 | NULL | NULL | 1 | 0 | ... ... ... | 0 | innodb_system | 1 | 1 | 1 | 1 | NULL | NULL | 1 | 0 | +-------+-------------------------------------------+-------------------+--------------------+-----------------+---------------------+--------------------------+------------------------------+----------------+----------------------+ reading Encryption key management MariaDB encryption supports multiple encryption keys, they are identified by a key identifier — a 32-bit integer. To support automatic key rotation every key additionally might have different versions. XtraDB and InnoDB can automatically re-encrypt the data from an older to a newer version of the same key. But how different keys are stored and rotated depends on the key management solution that you choose. but for this plugin file_key_management This plugin does not support key rotation — all keys always have the version 1. So I understand that I can't rotate the keys similar to what the AWS plugin provides. But if I need to change the key at any time, either just its encrypted form /etc/mariadb/keys.enc &/or the 'master' /etc/mariadb/keys.txt What's the procedure to re-key all the encrypted tables? Do I need to (1) stop the server (2) manually decrypt each table with its old key (3) reencrypt each table with the new key (4) restart the server ? True also for having used multiple keys for global/default, temp tables, and per-table? Is there any tool/procedure that automates that? I suppose that the AWS plugin takes care of that automated-rotation. Is there another non-commercial/open-source plugin with similar rotation capability?

3 4

[Maria-discuss] JSON column type
by Brent Clark 22 Feb '18

22 Feb '18

Good day Guys I have a client that is looking for JSON support, or better 'JSON column type'. He is asking for MySQL/5.7.8 (Currently on MySQL 5.6). And his comment is : "/This is so that we can use the JSON column type introduced in this version." We don't use MySQL, well we shipping away to MariaDB. The question I would like to ask is. Based on reading : https://mariadb.com/resources/blog/best-both-worlds-relational-json Is it fair to say, the clients needs are met? If anyone has any comment or further thought on this matter or any tips to share it would gratefully be appreciated. Regards and many thanks. Brent Clark

2 2

[Maria-discuss] mysqld_safe
by Ruben Safir 21 Feb '18

21 Feb '18

I did an update on my package manager and it seems that mysqld_safe was removed from the system, and I have that integrated into my openrc init system. Has it stopped being supported? ruben -- So many immigrant groups have swept through our town that Brooklyn, like Atlantis, reaches mythological proportions in the mind of the world - RI Safir 1998 http://www.mrbrklyn.com DRM is THEFT - We are the STAKEHOLDERS - RI Safir 2002 http://www.nylxs.com - Leadership Development in Free Software http://www2.mrbrklyn.com/resources - Unpublished Archive http://www.coinhangout.com - coins! http://www.brooklyn-living.com Being so tracked is for FARM ANIMALS and and extermination camps, but incompatible with living as a free human being. -RI Safir 2013

2 1

[Maria-discuss] build broken again -> Fwd: [MariaDB Announce] MariaDB 10.2.13, MariaDB Connector/ODBC 3.0.3 and MariaDB Connector/ODBC 2.0.16 now available
by Reindl Harald 14 Feb '18

14 Feb '18

can we have a release which simply builds? see my complaint about 10.2.12 10.2.13 is also broken different place would you guys mind sent out a link to the users list *before* GA annoucements so that such likely easy to fix bugs can be fixed *before* the announcement? and no it's not a option build with partition support and disable it in my.cnf because the next build won't start because the unknown option and i danced these dance now often enough while MariaDB is the only project in the whole opensource-ecosystem where can place a bet that the next release won't build with the same options Scanning dependencies of target mysqld Scanning dependencies of target explain_filename-t [ 99%] Building CXX object sql/CMakeFiles/mysqld.dir/main.cc.o [100%] Building CXX object unittest/sql/CMakeFiles/explain_filename-t.dir/explain_filename-t.cc.o [100%] Linking CXX executable mysqld [100%] Linking CXX executable explain_filename-t libsql.a(sql_yacc.cc.o): In function `MYSQLparse(THD*)': /home/buildbot/git/sql/sql_yacc.yy:5211: undefined reference to `partition_info::error_if_requires_values() const' collect2: error: ld returned 1 exit status make[2]: *** [sql/CMakeFiles/mysqld.dir/build.make:115: sql/mysqld] Error 1 make[1]: *** [CMakeFiles/Makefile2:8465: sql/CMakeFiles/mysqld.dir/all] Error 2 make[1]: *** Waiting for unfinished jobs.... ../../sql/libsql.a(sql_yacc.cc.o): In function `MYSQLparse(THD*)': /home/buildbot/git/sql/sql_yacc.yy:5211: undefined reference to `partition_info::error_if_requires_values() const' collect2: error: ld returned 1 exit status make[2]: *** [unittest/sql/CMakeFiles/explain_filename-t.dir/build.make:116: unittest/sql/explain_filename-t] Error 1 make[1]: *** [CMakeFiles/Makefile2:1336: unittest/sql/CMakeFiles/explain_filename-t.dir/all] Error 2 make: *** [Makefile:163: all] Error 2 Fehler: Fehler-Status beim Beenden von /var/tmp/rpm-tmp.Xg5GXO (%build) -------- Weitergeleitete Nachricht -------- Betreff: [Maria-discuss] Fwd: [MariaDB Announce] MariaDB 10.2.12 now available Datum: Thu, 4 Jan 2018 19:29:36 +0100 Von: Reindl Harald <h.reindl(a)thelounge.net> An: Mailing-List mariadb <maria-discuss(a)lists.launchpad.net> and once again a update don't build with the same rpm-spec as before - frankly how often should i offer that someone sends out a mail to the ML with a link to a proposed release tarball to get such things fixed *before* release? + cmake . -DFEATURE_SET=large -DCMAKE_INSTALL_PREFIX=/usr -DINSTALL_INCLUDEDIR=include/mysql -DINSTALL_LAYOUT=RPM -DDAEMON_NAME=mysqld -DDAEMON_NO_PREFIX=mysqld -DNICE_PROJECT_NAME=MariaDB -DINSTALL_LIBDIR=lib64/mysql -DINSTALL_MANDIR=share/man -DINSTALL_MYSQLSHAREDIR=share/mysql -DINSTALL_MYSQLTESTDIR=share/mysql-test -DINSTALL_PLUGINDIR=lib64/mysql/plugin -DINSTALL_SBINDIR=libexec -DINSTALL_SCRIPTDIR=bin -DINSTALL_SQLBENCHDIR= -DINSTALL_SUPPORTFILESDIR=share/mysql -DMYSQL_DATADIR=/var/lib/mysql -DMYSQL_UNIX_ADDR=/var/lib/mysql/mysql.sock -DENABLED_PROFILING=OFF -DENABLE_DEBUG_SYNC=OFF -DENABLE_DTRACE=OFF -DPLUGIN_ARIA=YES -DPLUGIN_CSV=YES -DPLUGIN_MYISAM=YES -DPLUGIN_ARCHIVE=NO -DPLUGIN_BLACKHOLE=NO -DPLUGIN_CASSANDRA=NO -DPLUGIN_CONNECT=NO -DPLUGIN_EXAMPLE=NO -DPLUGIN_FEDERATED=NO -DPLUGIN_FEDERATEDX=NO -DPLUGIN_FEEDBACK=NO -DPLUGIN_MROONGA=NO -DPLUGIN_MYISAMMRG=NO -DPLUGIN_OQGRAPH=NO -DPLUGIN_PARTITION=NO -DPLUGIN_PERFSCHEMA=NO -DPLUGIN_ROCKSDB=NO -DPLUGIN_SEMISYNC=NO -DPLUGIN_SEQUENCE=NO -DPLUGIN_SPHINX=NO -DPLUGIN_SPIDER=NO -DPLUGIN_TOKUDB=NO -DPLUGIN_XTRADB=NO -DWITHOUT_DYNAMIC_PLUGINS=ON -DWITH_ATOMIC_OPS=smp -DWITH_EMBEDDED_SERVER=OFF -DWITH_INNODB_DISALLOW_WRITES=OFF -DWITH_INNODB_BZIP2=OFF -DWITH_INNODB_LZ4=OFF -DWITH_INNODB_LZMA=OFF -DWITH_INNODB_LZO=OFF -DWITH_INNODB_SNAPPY=OFF -DWITH_MYSQLCOMPAT=ON -DSECURITY_HARDENED=OFF -DWITH_LIBARCHIVE=OFF -DWITH_LIBWRAP=OFF -DWITH_MARIABACKUP=OFF -DWITH_PIC=NO -DWITH_READLINE=OFF -DWITH_SAFEMALLOC=OFF -DWITH_VALGRIND=OFF -DWITH_WSREP=OFF -DWITH_JEMALLOC=OFF -DWITH_SSL=system -DWITH_ZLIB=system -DCOMPILATION_COMMENT=thelounge [ 99%] Built target sql Scanning dependencies of target explain_filename-t Scanning dependencies of target mysqld [ 99%] Building CXX object sql/CMakeFiles/mysqld.dir/main.cc.o [100%] Linking CXX executable mysqld [100%] Building CXX object unittest/sql/CMakeFiles/explain_filename-t.dir/explain_filename-t.cc.o [100%] Linking CXX executable explain_filename-t libsql.a(sql_yacc.cc.o): In function .`MYSQLparse.(/THD.*.)/'sql:/ libsql.a/(homesql_yacc.cc.o/)buildbot:/ Ingit /functionsql /`sql_yacc.yyMYSQLparse(:THD*5211):' :undefined /referencehome /tobuildbot /`gitpartition_info/sql:/:sql_yacc.yyerror_if_requires_values:5211(: )undefined referenceconst 'to `partition_info::error_if_requires_values() const' collect2: error: ld returned 1 exit status collect2: error: ld returned 1 exit status make[2]: *** [sql/CMakeFiles/mysqld.dir/build.make:115: sql/mysqld] Error 1 make[2]: *** [unittest/sql/CMakeFiles/explain_filename-t.dir/build.make:116: unittest/sql/explain_filename-t] Error 1 make[1]: *** [CMakeFiles/Makefile2:8464: sql/CMakeFiles/mysqld.dir/all] Error 2 make[1]: *** Waiting for unfinished jobs.... make[1]: *** [CMakeFiles/Makefile2:1336: unittest/sql/CMakeFiles/explain_filename-t.dir/all] Error 2 -------- Weitergeleitete Nachricht -------- Betreff: [MariaDB Announce] MariaDB 10.2.13, MariaDB Connector/ODBC 3.0.3 and MariaDB Connector/ODBC 2.0.16 now available Datum: Tue, 13 Feb 2018 21:03:01 +0200 Von: MariaDB Announce List <announce(a)mariadb.org> An: announce(a)mariadb.org The MariaDB project is pleased to announce the availability of MariaDB 10.2.13, the latest stable release in the MariaDB 10.2 series, MariaDB Connector/ODBC 3.0.3, the latest stable release in the MariaDB Connector/ODBC 3.0 series, and MariaDB Connector/ODBC 2.0.16, the latest stable release in the MariaDB Connector/ODBC 2.0 series. See the Release Notes and Changelogs for details. - - Links - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - MariaDB 10.2.13 - Release Notes: https://mariadb.com/kb/en/mdb-10213-rn/ - Changelog: https://mariadb.com/kb/en/mdb-10213-cl/ - Downloads: https://downloads.mariadb.org/mariadb/10.2.13 About MariaDB 10.2: - https://mariadb.com/kb/en/what-is-mariadb-102/ APT and YUM Repository Configuration Generator: - https://downloads.mariadb.org/mariadb/repositories/ MariaDB Connector/ODBC 3.0.3 - Release Notes: https://mariadb.com/kb/en/mco-303-rn/ - Changelog: https://mariadb.com/kb/en/mco-303-cl/ - Downloads: https://downloads.mariadb.org/connector-odbc/3.0.3/ MariaDB Connector/C 2.0.16 - Release Notes: https://mariadb.com/kb/en/mco-2016-rn/ - Changelog: https://mariadb.com/kb/en/mco-2016-cl/ - Downloads: https://downloads.mariadb.org/connector-odbc/2.0.16/ About MariaDB Connector/C: - https://mariadb.com/kb/en/about-mariadb-connector-c/ - - MariaDB Books - - - - - - - - - - - - - - - - - - - - - - - - - - There is an ever-growing library of MariaDB books available to help you get the most out of MariaDB. See the MariaDB Books page for details and links: - https://mariadb.com/kb/en/mariadb/books/ - - User Feedback plugin - - - - - - - - - - - - - - - - - - - - - - - MariaDB includes a User Feedback plugin. This plugin is disabled by default. If enabled, it submits basic, completely anonymous MariaDB usage information. This information is used by the developers to track trends in MariaDB usage to better guide development efforts. If you would like to help make MariaDB better, please add "feedback=ON" to your my.cnf or my.ini file! See http://mariadb.com/kb/en/user-feedback-plugin for more information. - - Quality - - - - - - - - - - - - - - - - - - - - - - - - - - - - - The project always strives for quality, but in reality, nothing is perfect. Please take time to report any issues you encounter at: - http://jira.mariadb.org - - Support MariaDB - - - - - - - - - - - - - - - - - - - - - - - - - If you would like to contribute to the MariaDB Foundation, please see the "contributing" and "donations" pages. We also have merchandise available in a cafepress store. All proceeds go to support the MariaDB Foundation. - https://mariadb.com/kb/en/contributing - https://mariadb.org/donate/ We hope you enjoy MariaDB! -- MariaDB Website - http://mariadb.org Twitter - http://twitter.com/mariadbfdn Knowledge Base - http://mariadb.com/kb

2 2

Re: [Maria-discuss] mariadb-backup meta deb package
by Reindl Harald 14 Feb '18

14 Feb '18

Am 14.02.2018 um 12:56 schrieb Florent B: > On 14/02/2018 12:49, Sergei Golubchik wrote: >> Hi, Florent! >> >> On Feb 14, Florent B wrote: >>> Hi, >>> >>> Wouldn't be nice to have a metapackage mariadb-backup in Debian >>> repository, that depends on the current best version >>> (mariadb-backup-10.2, etc..) ? >>> >>> Like "mariadb-server" package in fact. >> Yes, I guess. >> It'll be consistent with what we do with the server. >> >> Of course, if you also have a solution how to reduce the number of >> packages, that'd be perfect :) >> >> Hmm, how about that? >> We rename the following packages to remove "-10.1" at the end. >> >> mariadb-connect-engine-10.1 >> mariadb-oqgraph-engine-10.1 >> mariadb-cracklib-password-check-10.1 >> mariadb-gssapi-server-10.1 >> mariadb-gssapi-client-10.1 >> mariadb-backup-10.1 >> >> This way the server package will specify the version (either >> "mariadb-server-10.1" for 10.1 or "mariadb-server" for the latest) >> and everything else will follow. >> >> Looks logical and doesn't increase the number of packages (!!!). >> But I need to try whether it'll actually work in Debian :) > > Wow ! Someone understood what I mean. Thank you a lot Sergei, I though I > was crazy seeing other people's answers well, i don't get why there needs to be a metapackage at all http://yum.mariadb.org/10.1/rhel6-x86/rpms/ http://yum.mariadb.org/10.2/rhel6-x86/rpms/ these are different repos and you have either 10.1 or 10.2 enabled whatever packages in whatever versions are there, the update manager without mention a version explicit takes the one with the highest number independent of a new install or update %package server Summary: The MariaDB server and related files Requires: %{name} = %{epoch}:%{version}-%{release}, %{name}-libs = %{epoch}:%{version}-%{release} Requires: sh-utils Requires(pre): shadow-utils Provides: mysql-server = %{epoch}:%{version}-%{release}, mysql-server%{?_isa} = %{epoch}:%{version}-%{release} Obsoletes: mysql-server, community-mysql-server %description server "dnf install mysql-server" == "dnf install mariadb-server" == "dnf install community-mysql-server" why? because the Provides/Obsoletes in my spec say so

1 0