On Tue, 2017-04-04 at 10:54 -0500, David Bennett wrote: > I was under the impression that xtrabackup 2.2 was being removed from > stretch. Yes, it has already been removed from stretch and it is too late in the release cycle to get it back in because we are past the soft freeze. However, the package is still in Debian unstable so it should be updated rather than starting from scratch. The right way to do that is to join the Debian MySQL team and help with updating the package. Any package update in unstable should fix the 3 serious bugs that prevented its inclusion in Debian stretch. Since the exact same version is available in Debian jessie, you should fix those 3 serious bugs in jessie too, if they apply there, some may not due to dependencies. https://lists.debian.org/msgid-search/20170205222956.tgkvf222frsmsj7j@powdarrmonkey.net https://tracker.debian.org/pkg/percona-xtrabackup https://packages.qa.debian.org/p/percona-xtrabackup.html https://wiki.debian.org/Teams/MySQL https://www.debian.org/doc/manuals/developers-reference/pkgs.html#upload-stable https://www.debian.org/doc/manuals/developers-reference/pkgs.html#bug-security PS: I note that Percona XtraBackup seems to have some embedded code copies, please remove them from your VCS repository and tarballs. If they are modified, please get your patches upstreamed. https://wiki.debian.org/EmbeddedCodeCopies > Our intention is to jump directly to our 2.4.6 version which supports > Percona Server 5.6/5.7, MySQL 5.6/5.7, MariaDB 10.x. If you would > rather we upgrade the existing package to 2.4.6 this is fine. I'm not familiar with Percona XtraBackup so I'll leave the decision about which version use up to you and the MySQL team. For Debian's side, we usually choose to use the LTS version if there is one or the latest stable release otherwise. -- bye, pabs https://wiki.debian.org/PaulWise
Attachment:
signature.asc
Description: This is a digitally signed message part