Hello community, here is the log from the commit of package xtrabackup.1452 for openSUSE:12.3:Update checked in at 2013-03-21 11:16:31 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comparing /work/SRC/openSUSE:12.3:Update/xtrabackup.1452 (Old) and /work/SRC/openSUSE:12.3:Update/.xtrabackup.1452.new (New) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "xtrabackup.1452", Maintainer is "" Changes: -------- New Changes file: --- /dev/null 2013-02-26 18:15:11.936010755 +0100 +++ /work/SRC/openSUSE:12.3:Update/.xtrabackup.1452.new/xtrabackup.changes 2013-03-21 11:16:35.000000000 +0100 @@ -0,0 +1,243 @@ +------------------------------------------------------------------- +Thu Mar 14 23:27:30 UTC 2013 - andreas.stie...@gmx.de + +- update to 2.0.5 +- new features: + + New option --defaults-extra-file to read options before the + standard defaults-file, e.g. for separate username/passwords + crontab or a script somewhere in the system. +- bugs fixed: + + In case of streaming backups, innobackupex would resume the + XtraBackup process and then wait for it to finish before + running UNLOCK TABLES. This caused database to be unnecessarily + locked with FLUSH TABLES WITH READ LOCK. Innobackupex now waits + only till log copying is finished to unlock the databases. + + innobackupex error messages referencing the data directory + have been extended to show the path of the data directory + mentioned in the error message. + + Partitioned tables were not correctly handled by the + --databases, --include, --tables-file options of innobackupex, + and by the --tables and --tables-file options of XtraBackup. + + When built-in compression was used, XtraBackup was doing + unbuffered writes to the destination file or stream in very + small chunks which in return caused inefficient I/O. + + Unnecessary long sleep() in innobackupex lead to FLUSH TABLES + WITH READ LOCK taking too long. + + If innobackupex would crash it would leave the xtrabackup_suspended + file on the filesystem. This could then cause innobackupex to think + XtraBackup has suspended itself the moment it started, and then when + XtraBackup actually does suspend itself, innobackupex would wait for + it to end and wouldn’t re-remove the suspend file, leading to a wait + deadlock. + + innobackupex would fail to recognize MariaDB 5.2 and MariaDB 5.3 +- fix path of MySQL 5.5 xtrabackup binary [bnc#809505] + +------------------------------------------------------------------- +Wed Dec 5 21:02:57 UTC 2012 - andreas.stie...@gmx.de + +- update to 2.0.4 + + a regression introduced in XtraBackup 2.0.2 caused incremental + backups to fail because the init parameter values were not + normalized to the values used inside InnoDB + + a regression introduced in traBackup 2.0.2 didn’t take the + separate doublewrite tablespace into an account + + XtraBackup was handling the separate doublewrite buffer file + incorrectly. File path of the doublewrite buffer wasn’t added + to the backup-my.cnf and after the restore old doublewrite buffer + file was used instead of one made during the prepare stage + + XtraBackup now accepts the --innodb=force option, previously it + would throw an error if the option was set + + Option safe-slave-backup wasn’t working correctly + + In case safe-slave-backup-timeout was reached when using the + safe-slave-backup option, SQL_THREAD was left in stopped state + causing the slave thread to lag behind. This was fixed by + checking the initial SQL_THREAD state and starting it before + terminating with a timeout error and starting the SQL_THREAD + only if it was running initially. + + In case of streaming backups, innobackupex would resume the + Xtrabackup process and then wait for it to finish before running + UNLOCK TABLES. This caused database to be unnecessarily locked + with FLUSH TABLES WITH READ LOCK. Innobackupex now waits only + till log copying is finished to unlock the databases + + XtraBackup would fail on --apply-log when filesystem didn’t + support Linux AIO + + XtraBackup binary would ignore innodb_use_native_aio when it’s + specified either in my.cnf or as a command line option + + XtraBackup would print a warning message during the prepare + stage about innodb_file_io_threads being deprecated, even if the + variable wasn’t set + + XtraBackup Galera tests can now be run concurrently + +------------------------------------------------------------------- +Tue Oct 2 18:03:21 UTC 2012 - andreas.stie...@gmx.de + +- update to 2.0.3 +- new features: + * innobackupex now supports new --move-back option that can be used + instead of --copy-back in case there isn’t enough free disk space + on the server to copy files. As this option removes backup files, + it must be used with caution. +- bug fixes: + * Symlink for innobackupex-1.5.1 binary has been broken in the + previous version of XtraBackup. + * XtraBackup 2.0.2 was not backwards compatible which caused + incremental backups created with previous versions to fail on + prepare. + * Fix a regression that may potentially lead to a 5x increase in + disk space occupied by incremental backups. + * Fix a regression which caused incorrect handling of compressed + tablespaces with the page size of 16K, that were created between + the last full or incremental and the next incremental backup. +- packaging changes: + * improve upgrade from generic packages + +------------------------------------------------------------------- +Tue Aug 14 18:22:39 UTC 2012 - andreas.stie...@gmx.de + +- update to 2.0.2 + * Fixed false positive test suite failures with grep 2.10 + * Incremental backup would fail if a tablespace was created + between full and incremental backups. + * Assertion error in creating a compressed tablespace at delta + apply time has been fixed. + * If the table was renamed after the full backup, but before the + incremental backup has been taken, incremental backups would + fail when being prepared. + * When the variable innodb_log_block_size was set to 4096, backups + would fail in the prepare stage. + * Additional incremental backup tests have been added for the + incremental backup data page copy. +- update percona-xtrabackup-2.0.2-nodoc.patch + +------------------------------------------------------------------- +Sat Aug 4 08:55:08 UTC 2012 - andreas.stie...@gmx.de + +- add xtrabackup-nodoc.sh to source package - removes documentation + from pristine upstream source packages when maintaining package. + Not used during build or in binary package. + +------------------------------------------------------------------- +Fri Aug 3 07:31:50 UTC 2012 - andreas.stie...@gmx.de + +- remove documentation from MySQL and xtrabackup tarballs due to license + +------------------------------------------------------------------- +Sat Jul 7 13:46:00 UTC 2012 - andreas.stie...@gmx.de + +- update to 2.0.1: + * After creating a full compressed backup, performing a + compressed/uncompressed incremental backup would fail because + xtrabackup_checkpoints was compressed. This has been fixed by + omitting xtrabackup_checkpoints from compression, so that a full + backup could be used for incremental backups without decompression. + * --copy-back was copying compressed *.qp files as well. This has been + fixed by skipping the compressed files while copying the data back. + * Streaming backups with --stream=tar would fail if the file size was + bigger than 8GB. Fixed by changing the libarchive format from USTAR + to restricted PAX which supports bigger file sizes. + * innobackupex was calling the tar utility unconditionally when + streaming ib_lru_dump and xtrabackup_galera_info. Which led to a + broken stream when the xbstream format was used. + * when --compress was used together with --stream=tar, xtrabackup was + silently creating a broken backup. Now it fails with an error + instead, suggesting to either use xbstream, or don't use compression + at all. + * --safe-slave-backup was resulting in incorrect binlog info, because + in some cases innobackupex confused the response from SHOW SLAVE + STATUS with the one from SHOW MASTER STATUS. + * xbstream would sometimes fail while extracting the backup. + * innodb_data_file_path was not written to backup-my.cnf, this was a + regression introduced in previous version. + * XtraBackup would fail to find the datadir when using mysqld_multi. + This was fixed by adding new option --defaults-group, to both + innobackupex and xtrabackup, now it can be specified which section + of my.cnf to handle. + * InnoDB tables with names containing: opt, par, CSV, MYD were backed + up twice. These tables were backed up by xtrabackup binary and by + innobackupex script. Regular expression for filtering database + directory contents was fixed. + * When run innobackupex with --apply-log, it was reading configuration + from the server configuration file instead of backup-my.cnf in + backup directory. + * innobackupex could copy files to a wrong directory when merging an + incremental backup to a full one. + * Incremental backups were not working correctly with --stream=tar. + This was fixed by making --incremental-lsn incompatible with + --stream=tar. XtraBackup will fail with an error message suggesting + to use --stream=xbstream. + * innobackupex failed to copy-back backup if destination dir wasn't + empty. Exceptions were added for my.cnf and master.inf` as + XtraBackup doesn't backup those files, so it won't overwrite + anything. + * innobackupex --copy-back could skip some files when copying from a + Windows filesystem mounted over NFS. + * XtraBackup binary was leaking file descriptors on --backup. This was + fixed by reusing the existing file descriptor so no leak occurs. + * There were no source files in tar.gz archive for Percona XtraBackup + 2.0.0. + * XtraBackup|binary could fail with the log block checksum mismatch" + error when reading an partially written log block. + +------------------------------------------------------------------- +Tue May 29 06:01:14 UTC 2012 - andreas.stie...@gmx.de + +- cmake >= 2.6.3 is the actual minimum requirement, fixes 11.4 + +------------------------------------------------------------------- +Mon May 28 20:50:08 UTC 2012 - andreas.stie...@gmx.de + +- remove HTML documentation in favour of online documentation + to fix factory build, also simplifies license. +- require cmake >= 2.8.5 to catch this requirement in OBS earlier + when building for SLE + +------------------------------------------------------------------- +Wed Apr 25 18:44:01 UTC 2012 - andreas.stie...@gmx.de + +- add mysql-5.1.59.tar.gz ++++ 46 more lines (skipped) ++++ between /dev/null ++++ and /work/SRC/openSUSE:12.3:Update/.xtrabackup.1452.new/xtrabackup.changes New: ---- mysql-5.1.59-nodoc.patch mysql-5.1.59-nodoc.tar.gz mysql-5.5.17-nodoc.tar.gz percona-xtrabackup-2.0.2-nodoc.patch percona-xtrabackup-2.0.5-nodoc.tar.gz xtrabackup-nodoc.sh xtrabackup.changes xtrabackup.spec ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ xtrabackup.spec ++++++ # # spec file for package xtrabackup # # Copyright (c) 2013 SUSE LINUX Products GmbH, Nuernberg, Germany. # # All modifications and additions to the file contributed by third parties # remain the property of their copyright owners, unless otherwise agreed # upon. The license for this file, and modifications and additions to the # file, is the same license as for the pristine package itself (unless the # license for the pristine package is not an Open Source License, in which # case the license is the MIT License). An "Open Source License" is a # license that conforms to the Open Source Definition (Version 1.9) # published by the Open Source Initiative. # Please submit bugfixes or comments via http://bugs.opensuse.org/ # %define MYSQL_51_VERSION 5.1.59 %define MYSQL_55_VERSION 5.5.17 Summary: Online backup for MySQL / InnoDB License: GPL-2.0 Group: Productivity/Databases/Tools Name: xtrabackup Version: 2.0.5 Release: 0 Url: http://www.percona.com/software/percona-xtrabackup/ Source: percona-xtrabackup-%{version}-nodoc.tar.gz Source1: mysql-%{MYSQL_51_VERSION}-nodoc.tar.gz Source2: mysql-%{MYSQL_55_VERSION}-nodoc.tar.gz Source3: xtrabackup-nodoc.sh Patch0: percona-xtrabackup-2.0.2-nodoc.patch Patch1: mysql-5.1.59-nodoc.patch BuildRoot: %{_tmppath}/%{name}-%{version}-build # This is to ease migration from Percona's generic packages Provides: percona-xtrabackup = %{version} Obsoletes: percona-xtrabackup < %{version} # Requires: mysql BuildRequires: autoconf BuildRequires: automake BuildRequires: bison BuildRequires: cmake >= 2.6.3 BuildRequires: gcc BuildRequires: gcc-c++ BuildRequires: libaio-devel BuildRequires: libtool BuildRequires: ncurses-devel BuildRequires: openssl-devel BuildRequires: procps BuildRequires: pwdutils BuildRequires: readline-devel BuildRequires: tcpd-devel BuildRequires: zlib-devel %description Percona XtraBackup is an online (non-blocking) backup solution for InnoDB engines. It features uninterrupted transaction processing during backups for InnoDB, but can also backup MyISAM tables. %prep %setup -q -n percona-xtrabackup-%{version} -a 1 -a 2 # refuse to build from source tarballs with documentation due to license %__find -maxdepth 1 -type d -iname "doc*" -print && exit 1 %__find mysql-%{MYSQL_51_VERSION} -maxdepth 1 -type d -iname "doc*" -print && exit 1 %__find mysql-%{MYSQL_55_VERSION} -maxdepth 1 -type d -iname "doc*" -print && exit 1 %patch0 %patch1 %build set -ue export CFLAGS="$RPM_OPT_FLAGS" export CXXFLAGS="$RPM_OPT_FLAGS -fno-exceptions" export AUTO_DOWNLOAD=no ./utils/build.sh 5.1 %__cp src/xtrabackup_51 . %__cp src/xbstream . ./utils/build.sh innodb55 %__cp src/xtrabackup_innodb55 ./xtrabackup_55 %install install -d %{buildroot}%{_bindir} install -d %{buildroot}%{_datadir} install -m 755 xtrabackup_51 %{buildroot}%{_bindir} install -m 755 xtrabackup_55 %{buildroot}%{_bindir} install -m 755 xbstream %{buildroot}%{_bindir} install -m 755 innobackupex %{buildroot}%{_bindir} ln -s innobackupex %{buildroot}%{_bindir}/innobackupex-1.5.1 %files %defattr(-,root,root) %{_bindir}/innobackupex %{_bindir}/innobackupex-1.5.1 %{_bindir}/xtrabackup_51 %{_bindir}/xtrabackup_55 %{_bindir}/xbstream %doc COPYING %changelog ++++++ mysql-5.1.59-nodoc.patch ++++++ Index: mysql-5.1.59/configure.in =================================================================== --- mysql-5.1.59/configure.in.orig 2011-08-11 14:52:45.000000000 +0100 +++ mysql-5.1.59/configure.in 2012-08-03 07:58:20.000000000 +0100 @@ -2859,7 +2859,7 @@ AC_CONFIG_FILES(Makefile extra/Makefile sql/Makefile sql/share/Makefile dnl sql/sql_builtin.cc sql-common/Makefile dnl dbug/Makefile scripts/Makefile include/Makefile dnl - tests/Makefile Docs/Makefile support-files/Makefile dnl + tests/Makefile support-files/Makefile dnl support-files/MacOSX/Makefile support-files/RHEL4-SElinux/Makefile dnl server-tools/Makefile server-tools/instance-manager/Makefile dnl cmd-line-utils/Makefile cmd-line-utils/libedit/Makefile dnl Index: mysql-5.1.59/Makefile.am =================================================================== --- mysql-5.1.59/Makefile.am.orig 2012-08-03 08:03:02.000000000 +0100 +++ mysql-5.1.59/Makefile.am 2012-08-03 08:03:14.000000000 +0100 @@ -29,7 +29,7 @@ SUBDIRS = . include @docs_dirs@ @zlib_d mysql-test support-files sql-bench @tools_dirs@ \ win -DIST_SUBDIRS = . include Docs zlib \ +DIST_SUBDIRS = . include zlib \ cmd-line-utils sql-common scripts \ strings mysys dbug extra regex libmysql libmysql_r client unittest storage plugin \ vio sql man tests \ ++++++ percona-xtrabackup-2.0.2-nodoc.patch ++++++ The rpm spec file extracts the MySQL sources during %setup, make the build script work with that. Index: utils/build.sh =================================================================== --- utils/build.sh.orig 2012-08-07 17:04:50.000000000 +0100 +++ utils/build.sh 2012-08-14 19:18:52.000000000 +0100 @@ -80,7 +80,6 @@ AUTO_DOWNLOAD to \"yes\"" ################################################################################ function unpack_and_patch() { - tar xzf $top_dir/$1 cd `basename "$1" ".tar.gz"` patch -p1 < $top_dir/patches/$2 cd .. @@ -160,9 +159,6 @@ function build_all() server_tarball=mysql-$mysql_version.tar.gz innodb_dir=$server_dir/storage/$innodb_name - echo "Downloading sources" - auto_download $server_tarball - test -d $server_dir && rm -r $server_dir echo "Preparing sources" ++++++ xtrabackup-nodoc.sh ++++++ #!/bin/bash # # Remove documentation files from source archives # # Copyright (c) 2013 Andreas Stieger <andreas.stie...@gmx.de> # # All modifications and additions to the file contributed by third parties # remain the property of their copyright owners, unless otherwise agreed # upon. The license for this file, and modifications and additions to the # file, is the same license as for the pristine package itself (unless the # license for the pristine package is not an Open Source License, in which # case the license is the MIT License). An "Open Source License" is a # license that conforms to the Open Source Definition (Version 1.9) # published by the Open Source Initiative. # XTRABACKUP_VERSION=2.0.5 MYSQL51_VERSION=5.1.59 MYSQL55_VERSION=5.5.17 gunzip -v < percona-xtrabackup-${XTRABACKUP_VERSION}.tar.gz > percona-xtrabackup-${XTRABACKUP_VERSION}.tar && \ tar -v --delete -f percona-xtrabackup-${XTRABACKUP_VERSION}.tar "percona-xtrabackup-${XTRABACKUP_VERSION}/doc" && \ mv -v percona-xtrabackup-${XTRABACKUP_VERSION}.tar percona-xtrabackup-${XTRABACKUP_VERSION}-nodoc.tar && \ gzip -v percona-xtrabackup-${XTRABACKUP_VERSION}-nodoc.tar gunzip < mysql-${MYSQL51_VERSION}.tar.gz > mysql-${MYSQL51_VERSION}.tar && \ tar -v --delete -f mysql-${MYSQL51_VERSION}.tar "mysql-${MYSQL51_VERSION}/Docs" && \ mv -v mysql-${MYSQL51_VERSION}.tar mysql-${MYSQL51_VERSION}-nodoc.tar && \ gzip -v mysql-${MYSQL51_VERSION}-nodoc.tar gunzip < mysql-${MYSQL55_VERSION}.tar.gz > mysql-${MYSQL55_VERSION}.tar && \ tar -v --delete -f mysql-${MYSQL55_VERSION}.tar "mysql-${MYSQL55_VERSION}/Docs" && \ mv -v mysql-${MYSQL55_VERSION}.tar mysql-${MYSQL55_VERSION}-nodoc.tar && \ gzip -v mysql-${MYSQL55_VERSION}-nodoc.tar -- To unsubscribe, e-mail: opensuse-commit+unsubscr...@opensuse.org For additional commands, e-mail: opensuse-commit+h...@opensuse.org
