[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Accepted mysql-5.7 5.7.16-2 (source) into unstable



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Tue, 03 Jan 2017 07:44:43 +0100
Source: mysql-5.7
Binary: libmysqlclient20 libmysqld-dev libmysqlclient-dev mysql-client-core-5.7 mysql-client-5.7 mysql-server-core-5.7 mysql-server-5.7 mysql-server mysql-client mysql-testsuite mysql-testsuite-5.7 mysql-source-5.7
Architecture: source
Version: 5.7.16-2
Distribution: unstable
Urgency: medium
Maintainer: Debian MySQL Maintainers <pkg-mysql-maint@lists.alioth.debian.org>
Changed-By: Lars Tangvald <lars.tangvald@oracle.com>
Description:
 libmysqlclient-dev - MySQL database development files
 libmysqlclient20 - MySQL database client library
 libmysqld-dev - MySQL embedded database development files
 mysql-client - MySQL database client (metapackage depending on the latest versio
 mysql-client-5.7 - MySQL database client binaries
 mysql-client-core-5.7 - MySQL database core client binaries
 mysql-server - MySQL database server (metapackage depending on the latest versio
 mysql-server-5.7 - MySQL database server binaries and system database setup
 mysql-server-core-5.7 - MySQL database server binaries
 mysql-source-5.7 - MySQL source
 mysql-testsuite - MySQL regression tests
 mysql-testsuite-5.7 - MySQL 5.7 testsuite
Closes: 841592 844275 847231
Changes:
 mysql-5.7 (5.7.16-2) unstable; urgency=medium
 .
   * Fix the test main.grant_user_lock when run as root
     The test was to log in as anonymous user, but would use the current system
     user. This was ok in most cases, but failed when the test was run as root
     since root has its own mysql user by default.
     (Closes: #841592)
   * Fix invalid build flags being used by mysql_config
     mysql_config was pulling in build flags from the build environment, causing
     build failures in other packages if the environment contained invalid flags.
     It now uses a whitelist system instead.
     (Closes: #844275)
   * Limit number of mtr parallel tests based on aio-max-nr system setting
     On systems with many cores the test suite could fail or be unstable because
     each server needs a certain number of aio slots. Build now limits max test
     parallelization based on the max number of slots available on the system.
   * Fix upgrade issue from mysql-5.5 in Jessie
     An innochecksum file was moved from server to server-core in 5.7, causing
     file conflicts when upgrading.
     (Closes: #847231)
   * Added patch to fix failing test main.events_2
     The test uses a hardcoded date (2017-01-01), and fails after that date.
     The patch is temporary pending upstream fix of the test.
Checksums-Sha1:
 0249b7d7f891272350eb0dfd4e9cb1538ab0acd3 3213 mysql-5.7_5.7.16-2.dsc
 2dfc780382d3762e1b59b3b370085d8d9e1b7d85 3389688 mysql-5.7_5.7.16-2.debian.tar.xz
Checksums-Sha256:
 56aa64b6bf356f068e9e41fca92204ed5d38d1b284f931184a097b8b4cb14c5f 3213 mysql-5.7_5.7.16-2.dsc
 f936a2846fb61e0ec29e488fc8f4dc03503430bf508f8c5960fadbccffc609fb 3389688 mysql-5.7_5.7.16-2.debian.tar.xz
Files:
 940567923538855719705aa7b8f7c47e 3213 database optional mysql-5.7_5.7.16-2.dsc
 f835061f73c144a72eb483ae675c8b54 3389688 database optional mysql-5.7_5.7.16-2.debian.tar.xz

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCAAGBQJYa/cjAAoJEMAFfnFNaU+yf0QQANaAwyvgV/wHSHtRtrjSoWVE
TPBfGACvjChdN6Jo13wlJD6tiu+6VUTsQPecbclxSQQ9CZn3KylDUcvoz0w9czLy
MRj4QrEcnBpaV+yf1dGNfzG+VMoOJ0YhdU7yVmhqj3yt0TGOP39mXrEmf8IJteRh
zeMJ953CQTaZrFtclCgKFGeyP566VS/ByME/G02RPVFnOzHCjwrEsbO3M6CRRyxD
jLzceiMU4xkV2Bcd4ibuZ3hfQlrMy4i08SMUKkoLVuk/a7Fk4DXj7HQ1sc1Mes/x
ri9xvBlqsSe8+Oy1/dlUXzK9JRd2qfqIakRMymM3JM74rUFP8Mm3K3LgRXcPdWn5
/oXDFB9kcajvvc/k7thlmPg/OECF/NU6NZnrAXjZtzWxtKF9dINgJ/ZMXf2wZlN5
nB5I8ht2H2Z4JlqweekpalJ/OKXlkH0tUoKXTzqTq2LjzL4QGUkKuKGyGqwgu5dc
P6bMCdVrvemO310rlWZackr3qTcBOEiNx7RqyCR8fjpEmXMgM7KKjM/6cY13dDnz
ogohYKzNjnfZOvBxzaFdZuazOKOOGWiNYmfscsb+W0zLzMxWMV+xbE5/2VW2CQG0
KR1By0fNE366YRg8LI/to/Pybvl7MSXP4aX0vqkBtVGPp56AYM9Mg78xrvL0ejZC
z8iTQhJf8gJYhjNpjbhG
=vfew
-----END PGP SIGNATURE-----


Reply to: