Merge bugfix for #1172916
Bump version to 2.1.4
Use make dist for creating the source (RPM builder)
Revert functionality in the dpkg builder for building in any location

After the recent changes in the dpkg builder, functionality for building
outside the tree into any location was lost. Recover this functionality
while honoring the new changes.
Switch to --notransitional by default (dpkg builter)

Since the transitional package xtrabackup was just for helping in the
transition and it's not built in newer releases, switch its default to
not building, and add a new --transitional parameter to the builder that
enables it.
Switch --notransitional to be the default.
Use the exact revision for the source tarball name

Using a wildcard for the source tarball (ignoring its revision) could
cause problems in case of a dirty source directory. Use the exact name,
which we've got since we do know the revision.
Add a -D parameter to the dpkg packager for including the debian version

The new default after revision 609.3.3 is to use -1 as the package
suffix, but in order to include it in multi-distribution repos, we need
it to include the debian version as a suffix.

Add a -D parameter to the debian builder so it will include the debian
version instead of -1.
Merge release 2.1.4 branch
Bump version to 2.1.5.
Merge from trunk
Do not download the sources for "make dist" if DUMMY is set.
Implementation of
https://blueprints.launchpad.net/percona-xtrabackup/+spec/support-innodb-log-checksum-algorithm.

Also updated links in bootstrap.sh so Jenkins tests are executed against
Percona Server 5.6.14-62.0 and MySQL 5.6.14.
Automerge from 2.1.
Merged lp:~akopytov/percona-xtrabackup/support-innodb-log-checksum-algorithm-2.1.
Merged lp:~akopytov/percona-xtrabackup/support-innodb-log-checksum-algorithm-2.2.
Empty merge from 2.1.
update Debian packaging: uploaders, standards version and latest XB release
merge deb packaging updates to 2.2
Bug #1227240 fix.

my.cnf can contain innodb_log_arch_dir option for server. xtrabackup can
use servers my.cnf. As innodb_log_arch_dir option can be used only for backup
preparing xtrabackup exits with error message in the case of backup with
innodb_log_arch_dir option. Such behavior does not allow to make backup if
default my.cnf contains innodb_log_arch_dir.

This fix ignores --innodb_log_arch_dir and --to-archived-lsn and outputs warning
if --prepare is not set.