xtrabackup-2.4.10-bp150.1.3

- Remove unneeded patch:
  * percona-xtrabackup-2.4.9-aarch_buildfix.patch

- Percona XtraBackup 2.4.10:
  * Rebased to MySQL 5.7.19
  * Fix xbcrypt failure with --encrypt-key-file option
  * Fix lock-up on simultaneous usage of --lock-ddl and
  - -lock-ddl-per-table
  * Fix deadlock in prepare stage related to the maximum number
    of pending reads
  * Abort backup when encountering tablespaces with a corrupted
    first page instead of skipping
- Use %license (boo#1082318)

- compile some files with -O0 to allow build on aarch64
- add percona-xtrabackup-2.4.9-aarch_buildfix.patch
- add _constraints file: min 6G mem, min 8G diskspace

- Percona XtraBackup 2.4.9:
  * xbcrypt now has an ability to decrypt files in parallel by
    specifying the number of threads with the xtrabackup
  - -encrypt-threads option
  * xtrabackup --copy-back option can now be used with xtrabackup
  - -parallel option to copy the user data files in parallel (redo
    logs and system tablespaces are copied in the main thread)
  * Various fixes to slave_info writing
  * Various fixes for crashes under certain circumstances

- set default unix socket address to the mariadb socket location

- Percona XtraBackup 2.4.8:
  * Support MySQL 5.7, rebased to MySQL 5.7.13
  * Support for InnoDB tablespace encryption
    add --reencrypt-for-server-id option
  * Support SHA256 passwords (via SSL connection)
  * Support command options for secure connections
  * xbcrypt format changes, backups are incompatible with 2.3.x
  * Add --remove-original option to remove encrypted/compressed
    files after operations
  * Use hwardware accellerated crc32 implementaiton
  * Add options to exclude tables (--tables-exclude) and databases
    (--databases-exclude) from backup
  * xbstream now supports parallel extraction (--parallel)
  * xbstream now supports --decrypt, --encrypt-threads,
  - -encrypt-key, --encrypt-key-file for decryption
  * Add options for MDL locking (--lock-ddl, --lock-ddl-timeout,
  - -lock-ddl-per-table)
- packaging changes:
  * bundle boost 1.59.0
  * dropped patches:
    percona-xtrabackup-2.2.x-srv_buf_size.patch
    percona-xtrabackup-2.3.8-gcc7-fallthrough.patch
    percona-xtrabackup-2.3.8-gcc7-pointer-comparisons.patch

- Percona Xtrabackup 2.3.9:
  * New --check-privileges option to check for system privileges
  * Fix crash during prepare stage if index compaction was enabled
  * Support building with OpenSSL 1.1
  * xbstream could run out of file descriptors while extracting
    backups which contains many tables
  * Fix determining use of master_auto_postion on a slave to avoid
    generating an invalid xtrabackup_slave_info file
  * Fix crash backing up MariaDB 10.2.x with --ftwrl-* options
  * Along with xtrabackup_checkpints file, xtrabackup now copies
    xtrabackup_info file into directory specified by --extra-lsndir
  * GTID position was not recorded when --binlog-info option was
    set to AUTO
  * bundled, patched libarchive updated to 3.3.1

- Remove unused bundled libarchive windows build files with
  proprietary license keywords - bsc#1049458

- fix build with gcc7 bsc#1041250:
  * percona-xtrabackup-2.3.8-gcc7-fallthrough.patch
  * percona-xtrabackup-2.3.8-gcc7-pointer-comparisons.patch

- dont build shared libs for now.

- enable building with system ssl

- update to 2.3.8
  - New Features
  - Percona XtraBackup now uses hardware accelerated
    implementation of crc32 where it is supported.
  - Percona XtraBackup has implemented new options: xtrabackup
  - -tables-exclude and xtrabackup --databases-exclude that work
    similar to xtrabackup --tables and xtrabackup --databases
    options, but exclude given names/paths from backup.
  - The xbstream binary now supports parallel extraction with the
  - -parallel option.
  - The xbstream binary now supports following new options:
  - -decrypt, --encrypt-threads, --encrypt-key, and
  - -encrypt-key-file. When --decrypt option is specified
    xbstream will automatically decrypt encrypted files when
    extracting input stream. Either --encrypt-key or
  - -encrypt-key-file options must be specified to provide
    encryption key, but not both. Option --encrypt-threads
    specifies the number of worker threads doing the encryption,
    default is 1.
  - Bugs fixed
  - xtrabackup would not create fresh InnoDB redo logs when
    preparing incremental backup. Bug fixed #1669592.
  - xtrabackup --export can now export tables that have more than
    31 index. Bug fixed #1089681.
  - Unrecognized character \x01; marked by <-- HERE message could
    be seen if backups were taken with the version check enabled.
    Bug fixed #1651978.
- refreshed percona-xtrabackup-2.3.2-unbundle-jsnm.patch

- Percona XtraBackup 2.3.7
- New functionality:
  * new --remove-original option for removing the encrypted and
    compressed files once they’ve been decrypted/decompressed.
  * now supports -H, -h, -u and -p shortcuts for --hostname,
  - -datadir, --user and --password respectively.
- Bugs fixed:
  * used username set for the server in a configuration file even
    if a different user was defined in the user’s configuration file
  * Incremental backups did not include xtrabackup_binlog_info and
    xtrabackup_galera_info files
  * --move-back option did not always restore out-of-datadir
    tablespaces to their original directories
  * innobackupex and xtrabackup scripts were showing the password
    in the ps output when it was passed as a command line argument
    bsc#1026729
  * Incremental backup would fail with a path like ~/backup/inc_1
    because xtrabackup didn’t properly expand tilde

- Percona XtraBackup 2.3.6, including one security fix:
  * CVE-2016-6225: xbcrypt encryption IV not being set properly
    (boo#1019858)
- New functionality:
  * now supports SHA256 passwords
  * new supports command options for secure connections
- Bugs fixed:
  * intermittent assertion failures when not correctly identifying
    server version
  * Safe slave backup algorithm performed too short delays between
    retries which could cause backups to fail on a busy servers
  * fix compilation warnings with gcc6
  * Backup would still succeed even if xtrabackup would fail to
    write the metadata
  * xbcloud now supports EMC ECS Swift API Authorization requests
  * backup failed with MariaDB 10.2 with the unsupported server
    version error message

- Percona XtraBackup 2.3.5, a bugfix release:
  * Backup process would fail if --throttle option was used
  * .ibd files for remote tablespaces were not copied back to the
    original location pointed by the .isl files.
  * Fix crash when called with insufficient parameters, like
    specifying the empty --defaults-file option
  * Change default value of --ftwrl-wait-query-type from "all" to
    "update"
  * Allow the datadir from my.cnf to override the one from
    SHOW VARIABLES
  * Fix failure on MariaDB if binary logs were in non-standard
    directory
- Includes changes from 2.3.4:
  * respect variables in backup-my.cnf without having to specify
  - -defaults-file=backup-my.cnf
  * abort the backup if innobackupex --rsync completed with error
  * Fix logging ouf GTID info with MariaDB 10
  * Fix silent skipping of extra arguments
  * Allow connections to servers using legacy auth with new option
  - -skip-secure-auth

- Fix Group tag.

- Percona XtraBackup 2.3.3, a bugfix release:
  * Database directories were not removed if DROP DATABASE happened
    during the backup.
  * Backup would fail if Store backup history on the server feature
    was enabled and backup was taken from server without binary
    log enabled.
  * Percona XtraBackup now fails with descriptive error message if
  - -defaults-extra-file is not specified first.
  * Backup would fail if --rsync option was used without specifying
    temporary folder.
  * Fixed Percona XtraBackup crash which happened when it was used
    for SST on MariaDB Galera Cluster caused by double free of
    datadir? variable.
  * --move-back did not respect the innodb_log_group_home_dir and
    innodb_data_home_dir options which caused ib_logfiles and data
    files not to be moved to correct location.
  * xtrabackup_binlog_info was not updated correctly when applying
    incremental backups.
  * When using a --defaults-file option Percona XtraBackup would
    complain about datadir being mismatched if it wasn?t explicitly
    set in the defaults file.
  * Fixed build issues by adding missing check in cmake script for
    xxd presence.
  * Percona XtraBackup would terminate backup process without error
    if --slave-info option was used on a server not running as a
    replication slave.
  * innobackupex when used with --stream option would create an
    empty directory with a timestamp as a name.
- update percona-xtrabackup-2.3.2-disable-version-check.patch
  to percona-xtrabackup-2.3.3-disable-version-check.patch

- xtrabackup does not strictly require mysqld, and this capability
  is not longer provided by development MariaDB packages boo#959917

- Percona XtraBackup 2.3.2, a feature release:
  * New utility xbcloud:
    + for up/downloading xbstream archives from/to cloud storage.
    + reads settings from [xbcloud] section in {/etc/,.}my.cnf
  * Backwards compatibility:
    + The innobackupex script was rewritten in C and is a symlink
    for xtrabackup. 2.2 command syntax is supported but
    deprecated. Syntax for new features added to xtrabackup only.
    + Options: --lock-wait-query-type, --lock-wait-threshold and
  - -lock-wait-timeout have been renamed to innobackupex
  - -ftwrl-wait-query-type, --ftwrl-wait-threshold and
  - -ftwrl-wait-timeout respectively.
  * command line options changed to follow MySQL guidelines
  * xtrabackup now also copies MyISAM tables and supports every
    feature of innobackupex
  * xtrabackup now supports --datadir
  * Various bug fixes and improvements
- drop percona-xtrabackup-2.2.x-disable-default-version-check.patch
- add percona-xtrabackup-2.3.2-disable-version-check.patch to
  remove feature completely
- unbundle the jsnm library,
  adding percona-xtrabackup-2.3.2-unbundle-jsnm.patch

- Percona XtraBackup 2.2.13, a bugfix release:
  * Improved the detection when the log block that has the different
    number from what is expected
  * Fixed false positive error: The log was not applied to the
    intended LSN which was happening even when the redo log was
    applied correctly
  * xtrabackup_logfile was not compressed when --compress option was
    used. Bug fixed #1242309.
  * innobackupex wrote error message to STDOUT instead of STDIN
    which broke xbstream and tar stream.
  * Incremental backups did not work with MariaDB below 10.1.6.