[Bug 1961617] Re: String returned when DATETIME expected
I think this is the same issue as reported in https://bugs.mysql.com/bug.php?id=106352 (which will be fixed in upcoming 8.0.29) ** Bug watch added: MySQL Bug System #106352 http://bugs.mysql.com/bug.php?id=106352 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961617 Title: String returned when DATETIME expected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1961617/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961617] Re: String returned when DATETIME expected
We're looking into it, will get back to you when I know more :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961617 Title: String returned when DATETIME expected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1961617/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914636] Re: package mysql-server-8.0 8.0.23-0ubuntu0.20.04.1 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1
The script in /var/lib/mysql-files seems very old; We do something similar now, but the "install plugin" line was removed, because that line will return an error if the plugin is already installed, aborting the script before it reaches shutdown, thus causing the installation to hang. If that file is somehow set to be used it could cause a hang, but it would either need to be specified in the config file (which we've never done automatically) or somehow have the filename postinst expects to find (which we generate with mktemp --tmpdir /var/lib/mysql-files). So not entirely sure what's happened here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914636 Title: package mysql-server-8.0 8.0.23-0ubuntu0.20.04.1 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1914636/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915004] Re: Please sync mysql 8.0.23-1 from debian
Closing because the sync has already been done (just stuck in proposed) ** Changed in: mysql-8.0 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915004 Title: Please sync mysql 8.0.23-1 from debian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1915004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915004] [NEW] Please sync mysql 8.0.23-1 from debian
Public bug reported: Source package: mysql-8.0 Version to sync: 8.0.23-1 Sync from: Debian sid main There are only two changes missing from mysql-8.0.23-0ubuntu.20.10.1: - Use system libs by default (https://salsa.debian.org/mariadb- team/mysql/-/commit/ac979f2dae52ce3a25d4ba26a767edf334767b95): Will automatically use system versions of dependencies instead of bundled versions, where possible - Remove timeout limit for systemd service (https://salsa.debian.org /mariadb-team/mysql/-/commit/cfee6a8bc14258011449a99d8a80b22c5a093a50): This is a fix for https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1882527 ** Affects: mysql-8.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915004 Title: Please sync mysql 8.0.23-1 from debian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1915004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911032] Re: autopkgtest fails in 2021
I have a fix for this at https://salsa.debian.org/mariadb- team/mysql/-/commit/a0310990d8c2c892879306cadc8516d8d04e4780 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911032 Title: autopkgtest fails in 2021 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1911032/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899248] Re: package mysql-server-8.0 8.0.21-0ubuntu0.20.04.4 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1
Typo: It waits 60 seconds, not a second -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899248 Title: package mysql-server-8.0 8.0.21-0ubuntu0.20.04.4 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1899248/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899248] Re: package mysql-server-8.0 8.0.21-0ubuntu0.20.04.4 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1
Looking at that part of the postinst code, we have some oold logic for doing server shutdowns that waits a second for mysqld to stop, and 8.0 is slower to startup and shutdown than older versions, so it may simply be hitting a timeout without there strictly being anything wrong. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899248 Title: package mysql-server-8.0 8.0.21-0ubuntu0.20.04.4 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1899248/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899248] Re: package mysql-server-8.0 8.0.21-0ubuntu0.20.04.4 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1
I'll do some testing. I'm not 100% sure the mysqlx.sock error is fatal. The server log seems to end with a successful startup. >From terminal: mysqld is running as pid 21763 Error: Unable to shut down server with process id 21763 dpkg: error processing package mysql-server-8.0 (--configure): installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899248 Title: package mysql-server-8.0 8.0.21-0ubuntu0.20.04.4 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1899248/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899248] Re: package mysql-server-8.0 8.0.21-0ubuntu0.20.04.4 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1
iirc, we had a bug earlier where the apparmor profile was missing the mysqlx.sock file (new in 8.0), but that doesn't seem to be the case here, and no apparmor errors on it in the dmesg file. I'm not sure if it's relevant, but there's an apparmor error for snap with docker and mysql mentioned. The error itself doesn't tell me much, but can you verify that you're not running mysql in a snap or docker container with socket files and/or ports mapped to the host? Another process already having written the mysql.sock file might explain the issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899248 Title: package mysql-server-8.0 8.0.21-0ubuntu0.20.04.4 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1899248/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1889851] Re: Driver QMysql can't be loaded
A simpler fix is to add a cmake flag to override the tls-model flag: -DCMAKE_CXX_FLAGS="-ftls-model=global-dynamic" \ to debian/rules -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1889851 Title: Driver QMysql can't be loaded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1889851/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1889851] Re: Driver QMysql can't be loaded
Verified that reverting the commit Marc suggested makes the test case pass. If I understand it correctly, STATIC_TLS is a limited resource, so if the python wrapping loads other libraries that also use it, but your c program doesn't? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1889851 Title: Driver QMysql can't be loaded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1889851/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1889851] Re: Driver QMysql can't be loaded
Verified with upstream packages as well. The test case also works as expected with 8.0.20, so it was introduced in 8.0.21. I'll do a test build to see if reverting that commit fixes it. Thanks for the tip, Marc :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1889851 Title: Driver QMysql can't be loaded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1889851/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1889851] Re: Driver QMysql can't be loaded
Thanks for the report and test case! I'll test it, and pass it on upstream. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1889851 Title: Driver QMysql can't be loaded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1889851/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1889472] Re: mysql-server-5.7 postinst fails when in read-only mode
Hi Simon, Would it help for you to manually trigger "freeze mode"? This was added as a way to stop automatic management of the service in case of some unrecoverable issue with it, without triggering apt errors. If you create the file /etc/mysql/FROZEN (if you're installing in interactive mode you should get a debconf message about this), it should skip most of the postinst script, so it won't start the service, run mysql_upgrade, etc, but you should get all the unit and config files so you can easily init and start it up yourself. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1889472 Title: mysql-server-5.7 postinst fails when in read-only mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1889472/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884809] [NEW] libmysqlclient21 crashes if certain collation definitions are found in MySQL's sharedir
Public bug reported: Note: This was originally reported as https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1877504, but that bug contains discussions about multiple separate issues, which are not fully resolved by this fix. [Impact] libmysqlclient21 does not by default include any charset files in Ubuntu, but it will use charset files found in /usr/share/mysql/ If the usr/share/mysql/Index.xml file contains a charset definition with a certain combination of collations, it can cause a segmentation fault in libmysqlclient21. The default charset files in MySQL do not cause this problem, but those from MariaDB do. So a user running e.g. mythtv (which is built with libmysqlclient21) with MariaDB as the underlying server package can encounter crashes. The segmentation fault does not happen with 8.0.19, so this is a regression from earlier versions. [Test Case] * Install libmysqlclient21, libmysqlclient-dev and mysql-server * Connect to the database with "sudo mysql" and run the attached init.sql (just creates a test user with access to a test database) * Compile attached mysql_test.c (file has full gcc command needed) * Run the mysql_test program. It will output a few lines (contents of test table) * Now replace /usr/share/mysql/charsets/Index.xml with the attached one * Run the mysql_test program. It will produce a segmentation fault [Regression Potential] The patch itself only blocks out a single function call on a pointer if that pointer is null, but it doesn't fix the underlying issue of the charset parser picking up unexpected definition files (but this problem is present in versions prior to 8.0.20 as well) ** Affects: mysql-8.0 (Ubuntu) Importance: Undecided Status: New ** Description changed: Note: This was originally reported as https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1877504, but that bug contains discussions about multiple separate issues, which are not fully resolved by this fix. [Impact] libmysqlclient21 does not by default include any charset files in Ubuntu, but it will use charset files found in /usr/share/mysql/ If the usr/share/mysql/Index.xml file contains a charset definition with a certain combination of collations, it can cause a segmentation fault in libmysqlclient21. The default charset files in MySQL do not cause this problem, but those from MariaDB do. So a user running e.g. mythtv (which is built with libmysqlclient21) with MariaDB as the underlying server package can encounter crashes. + The segmentation fault does not happen with 8.0.19, so this is a regression from earlier versions. [Test Case] * Install libmysqlclient21, libmysqlclient-dev and mysql-server * Connect to the database with "sudo mysql" and run the attached init.sql (just creates a test user with access to a test database) * Compile attached mysql_test.c (file has full gcc command needed) * Run the mysql_test program. It will output a few lines (contents of test table) * Now replace /usr/share/mysql/charsets/Index.xml with the attached one * Run the mysql_test program. It will produce a segmentation fault [Regression Potential] The patch itself only blocks out a single function call on a pointer if that pointer is null, but it doesn't fix the underlying issue of the charset parser picking up unexpected definition files (but this problem is present in versions prior to 8.0.20 as well) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884809 Title: libmysqlclient21 crashes if certain collation definitions are found in MySQL's sharedir To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1884809/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877442] Re: Broken SQL CONCAT function behaviour in 5.7.30-0ubuntu0.18.04.1
** Description changed:
+ [Impact]
+ This is a regression in MySQL 5.7.30 (does not affect 8.0 which is in focal
and development release, nor 5.7.29). The CONCAT function has inconsistent
behavior depending on whether or not the result is assigned to a variable,
which is leading to a crash in slurmdbd.
+
+ [Test Case]
+ Run the following two queries:
+
+ - SELECT CONCAT('');
+ - SET @var = ""; SELECT @var := CONCAT('');
+ They should give the same output, but the second one returns NULL instead of
an empty string when using 5.7.30.
+
+ [Regression Potential]
+ The patch changes fairly low-level code, which can always carry some risk.
The patch will also need to be removed if next upstream release (5.7.31) is
picked, since it will have its own fix for this issue.
+
+
+ --- ORIGINAL DESCRIPTION ---
Hi,
Yesterday we upgraded from 5.7.29-0ubuntu0.18.04.1 to
5.7.30-0ubuntu0.18.04.1 (via unattended-upgrade) on Ubuntu 18.04 and
slurmdbd (https://packages.ubuntu.com/bionic/admin/slurmdbd) started
segfaulting.
Upon inspection, the slurmdbd crash is caused by a change of behaviour
of the SQL CONCAT function. The new behaviour seems wrong.
Calling
SELECT CONCAT('');
will result in an empty string as expected however if the result is assigned
to a variable with:
SET @var = ""; SELECT @var := CONCAT('');
the variable will be NULL instead of an empty string.
It seems that when the output of CONCAT is assigned to a variable; if
CONCAT should have returned an empty string, it will set the variable to
NULL instead.
SLURM itself crashes because it uses a stored procedure which relies on
the output of CONCAT to be an empty string rather than a NULL variable
and tries to dereference the pointer.
I wasn’t able to get hold of 5.7.29-0ubuntu0.18.04.1 via APT so I tested
on 5.7.21-1ubuntu1. On 5.7.21, the variable was correctly set to an
empty string. I have also tried on 20.04 and the behaviour is correct as
well. So the problem seems to be present only in the version
5.7.30-0ubuntu0.18.04.1.
I think that the behaviour was introduced in the 5.7 branch by this commit:
https://github.com/mysql/mysql-server/commit/addb2aab601d98e685eccae545f79d120561ad9b
but I am not entirely sure.
This bug is a bit annoying because it makes SLURM with accounting
enabled completely unusable. However downgrading MySQL to
5.7.29-0ubuntu0.18.04.1 temporarily fixed the problem.
I have attached a log file with examples to reproduce the bug.
Thank you very much.
** Description changed:
[Impact]
This is a regression in MySQL 5.7.30 (does not affect 8.0 which is in focal
and development release, nor 5.7.29). The CONCAT function has inconsistent
behavior depending on whether or not the result is assigned to a variable,
which is leading to a crash in slurmdbd.
+ Since it's limited to 5.7.30, the bug only affects stable releases
+ Bionic and Xenial.
+
[Test Case]
- Run the following two queries:
-
- - SELECT CONCAT('');
- - SET @var = ""; SELECT @var := CONCAT('');
+ - Start up MySQL Server 5.7.30
+ - Connect to it with the mysql cli (with default install of the server, "sudo
mysql" will connect to the MySQL root user)
+ - Run the following two queries:
+ * SELECT CONCAT('');
+ * SET @var = ""; SELECT @var := CONCAT('');
They should give the same output, but the second one returns NULL instead of
an empty string when using 5.7.30.
[Regression Potential]
- The patch changes fairly low-level code, which can always carry some risk.
The patch will also need to be removed if next upstream release (5.7.31) is
picked, since it will have its own fix for this issue.
+ The patch changes fairly low-level code, which can always carry some risk.
+ [Other info]
+ This bug is fixed in the next upstream release of MySQL (5.7.31), so the
patch would only be needed until that is picked.
--- ORIGINAL DESCRIPTION ---
Hi,
Yesterday we upgraded from 5.7.29-0ubuntu0.18.04.1 to
5.7.30-0ubuntu0.18.04.1 (via unattended-upgrade) on Ubuntu 18.04 and
slurmdbd (https://packages.ubuntu.com/bionic/admin/slurmdbd) started
segfaulting.
Upon inspection, the slurmdbd crash is caused by a change of behaviour
of the SQL CONCAT function. The new behaviour seems wrong.
Calling
SELECT CONCAT('');
will result in an empty string as expected however if the result is assigned
to a variable with:
SET @var = ""; SELECT @var := CONCAT('');
the variable will be NULL instead of an empty string.
It seems that when the output of CONCAT is assigned to a variable; if
CONCAT should have returned an empty string, it will set the variable to
NULL instead.
SLURM itself crashes because it uses a stored procedure which relies on
the output of CONCAT to be an empty string rather than a NULL variable
and tries to dereference the pointer.
I wasn’t able to get hold of 5.7.29-0ubuntu0.18.04.1 via APT so I tested
on
[Bug 1877442] Re: Broken SQL CONCAT function behaviour in 5.7.30-0ubuntu0.18.04.1
I've tested a patch that fixes this issue now. Will try to get a fix in (though it will also be fixed in the next upstream release). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877442 Title: Broken SQL CONCAT function behaviour in 5.7.30-0ubuntu0.18.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1877442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877504] Re: new version of libmysqlclient21 8.0.20-0ubuntu0.20.04.1 causes mythtv-set, mythbackend and mythfrontend to segfault on exit.
@Otto The usr/share/mysql/charsets/Index.xml file from mysql 5.7 (or older versions of 8.0) does not cause this issue. MySQL does not and has never had any MariaDB compatibility, and can not be expected to work properly if internal MySQL files are replaced by ones from MariaDB. That said, this is still a regression bug in MySQL's charset parser (not a deliberate change), which we are fixing (afaik, the charset definition that triggers this is not invalid). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1877504 Title: new version of libmysqlclient21 8.0.20-0ubuntu0.20.04.1 causes mythtv- set, mythbackend and mythfrontend to segfault on exit. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mariadb-10.3/+bug/1877504/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877183] Re: segfault in mysql_server_end() from libmysqlclient.so.21
*** This bug is a duplicate of bug 1877504 *** https://bugs.launchpad.net/bugs/1877504 Right. This was reported first, but most of the discussion was there, so I'll mark this as a duplicate (as noted in the other report, this is a combination of a bug in mysql and maria still using mysql paths for incompatible files). ** This bug has been marked a duplicate of bug 1877504 new version of libmysqlclient21 8.0.20-0ubuntu0.20.04.1 causes mythtv-set, mythbackend and mythfrontend to segfault on exit. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877183 Title: segfault in mysql_server_end() from libmysqlclient.so.21 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1877183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877504] Re: new version of libmysqlclient21 8.0.20-0ubuntu0.20.04.1 causes mythtv-set, mythbackend and mythfrontend to segfault on exit.
Thanks for the help! I'm running build with the patch I have to prevent the segfault as well, so it shouldn't be quite as vulnerable to this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1877504 Title: new version of libmysqlclient21 8.0.20-0ubuntu0.20.04.1 causes mythtv- set, mythbackend and mythfrontend to segfault on exit. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mariadb-10.3/+bug/1877504/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877442] Re: Broken SQL CONCAT function behaviour in 5.7.30-0ubuntu0.18.04.1
This bug is actually only in 5.7.30, not 8.0.20 (not 100% sure if we made a mistake marking it as fixed in 8.0.21 unless there was some underlying issue that only triggered the NULL result in 5.7) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877442 Title: Broken SQL CONCAT function behaviour in 5.7.30-0ubuntu0.18.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1877442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877504] Re: new version of libmysqlclient21 8.0.20-0ubuntu0.20.04.1 causes mythtv-set, mythbackend and mythfrontend to segfault on exit.
Simply doing "if (cs && cs->coll && cs->coll->uninit) {" fixes the
segfault in the test case, so I just need to check with a dev if that's
a sane way to handle this (or if I'd just be hiding the symptom)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1877504
Title:
new version of libmysqlclient21 8.0.20-0ubuntu0.20.04.1 causes mythtv-
set, mythbackend and mythfrontend to segfault on exit.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1877504/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877504] Re: new version of libmysqlclient21 8.0.20-0ubuntu0.20.04.1 causes mythtv-set, mythbackend and mythfrontend to segfault on exit.
Thanks for looking into it more. This might be what the devs need, so I'll pass it on (I've been trying to figure out exactly what causes it to work with upstream's package (or a libmysqlclient21 built just plainly with cmake, make, make install), but no luck. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1877504 Title: new version of libmysqlclient21 8.0.20-0ubuntu0.20.04.1 causes mythtv- set, mythbackend and mythfrontend to segfault on exit. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1877504/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877504] Re: new version of libmysqlclient21 8.0.20-0ubuntu0.20.04.1 causes mythtv-set, mythbackend and mythfrontend to segfault on exit.
This is probably the same as https://bugs.launchpad.net/ubuntu/+source /qtbase-opensource-src/+bug/1877183 I'll experiment a bit and see if maybe there are any compiler flags we use that are causing this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1877504 Title: new version of libmysqlclient21 8.0.20-0ubuntu0.20.04.1 causes mythtv- set, mythbackend and mythfrontend to segfault on exit. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1877504/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877504] Re: new version of libmysqlclient21 8.0.20-0ubuntu0.20.04.1 causes mythtv-set, mythbackend and mythfrontend to segfault on exit.
Hm, if I install upstream's libmysqlclient21_8.0.20, there's no segfault. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1877504 Title: new version of libmysqlclient21 8.0.20-0ubuntu0.20.04.1 causes mythtv- set, mythbackend and mythfrontend to segfault on exit. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1877504/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877504] Re: new version of libmysqlclient21 8.0.20-0ubuntu0.20.04.1 causes mythtv-set, mythbackend and mythfrontend to segfault on exit.
Thanks for the test case. Connecting to a mariadb server isn't supported (and thus not tested at all), but segfaulting is pretty bad, so hopefully we can get this fixed with all the information you've provided. It's important to note, though, that MariaDB and MySQL diverge more and more with every release, and at some point they will most likely no longer work together at all. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1877504 Title: new version of libmysqlclient21 8.0.20-0ubuntu0.20.04.1 causes mythtv- set, mythbackend and mythfrontend to segfault on exit. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1877504/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877183] Re: segfault in mysql_server_end() from libmysqlclient.so.21
Having trouble reproducing this: $ ./test About to remove database Removed database I don't know much about QT, so just did the bare minimum to get the test case built. Did you build or run the test case in any particular way? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877183 Title: segfault in mysql_server_end() from libmysqlclient.so.21 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1877183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877442] Re: Broken SQL CONCAT function behaviour in 5.7.30-0ubuntu0.18.04.1
Verified as upstream bug: https://bugs.mysql.com/bug.php?id=99485 ** Bug watch added: MySQL Bug System #99485 http://bugs.mysql.com/bug.php?id=99485 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877442 Title: Broken SQL CONCAT function behaviour in 5.7.30-0ubuntu0.18.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1877442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877442] Re: Broken SQL CONCAT function behaviour in 5.7.30-0ubuntu0.18.04.1
Thanks for the report and the testcase! I'll pass it on upstream. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877442 Title: Broken SQL CONCAT function behaviour in 5.7.30-0ubuntu0.18.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1877442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872541] Re: MySQL client fails to connect, seems to force SSL
The problem with using ssl is that you are using a client (openssl 1.1 .1f-based) that will not speak anything older than TLS 1.2, trying to connect to a server that can only speak TLS 1.1. >From 1.1.1f-1ubuntu1 changelog entry >(https://launchpad.net/ubuntu/+source/openssl/+changelog): - Set OPENSSL_TLS_SECURITY_LEVEL=2 as compiled-in minimum security level. Change meaning of SECURITY_LEVEL=2 to prohibit TLS versions below 1.2 and update documentation. Previous default of 1, can be set by calling SSL_CTX_set_security_level(), SSL_set_security_level() or using ':@SECLEVEL=1' CipherString value in openssl.cfg. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872541 Title: MySQL client fails to connect, seems to force SSL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1872541/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872541] Re: MySQL client fails to connect, seems to force SSL
This also fits with seeing the same problem for a 5.7.21 server, which was also built with yaSSL. Could you test updating your docker image server to the newest 5.7 and see if that fixes it? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872541 Title: MySQL client fails to connect, seems to force SSL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1872541/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872541] Re: MySQL client fails to connect, seems to force SSL
Mariadb client is built with gnutls, I believe. I was able to reproduce this now. If you install an older mysql server from before 5.6 also used openssl (5.6.44 in my case), then enable ssl on the server, you get the error reported when trying to connect to it from Ubuntu 20.04 8.0 client. The user you try to connect to doesn't need to have any special settings on it. Upgrading to 5.6.47 fixed the issue for me, so I'm guessing this is because 5.6.44 was built with yassl, which is old and unsupported (again, I don't know exactly what Amazon does, so needs verifying). The cause might be that yassl only supports TSL 1.1, while Ubuntu with the update to OpenSSL 1.1.1f has started enforcing 1.2 as the minimum version (if I'm reading the changelog correctly). I don't think this is a bug. Only fix would be setting ssl-mode to DISABLED in the client config or getting the server updated (which as you said is outside your control) to one that isn't built with yaSSL. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872541 Title: MySQL client fails to connect, seems to force SSL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1872541/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872541] Re: MySQL client fails to connect, seems to force SSL
ssl-mode should default to a mode that tries to autodetect server support, with automatic fallback to disabled(PREFERRED, per https://dev.mysql.com/doc/refman/8.0/en/connection-options.html #option_general_ssl-mode), but I'm not sure if that works properly with the Aurora server. Have you looked at https://aws.amazon.com/premiumsupport/knowledge- center/rds-error-2026-ssl-connection/? The error message you get doesn't quite match what is mentioned there or what MySQL would report if the problem was that the client tried to enforce ssl, but I did find https://github.com/microsoft/msphpsql/issues/1023 which also mentions it working in 19.10 but no longer in 20.04. Maybe something related to openssl 1.1.1f? ** Bug watch added: github.com/microsoft/msphpsql/issues #1023 https://github.com/microsoft/msphpsql/issues/1023 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872541 Title: MySQL client fails to connect, seems to force SSL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1872541/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872541] Re: MySQL client fails to connect, seems to force SSL
I can't reproduce this with a regular (upstream) 5.6 server; Can run a 5.6 server on a debian 9 host and connect to it fine from a 20.04 running 8.0. What is the auth type of the user in the mysql.user table? Does the same thing happen if you create a new user with just a normal password auth? I don't really know what the state of the AWS server would be (upstream is on 5.6.47, but the versions aren't directly comparable I think). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872541 Title: MySQL client fails to connect, seems to force SSL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1872541/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872541] Re: MySQL client fails to connect, seems to force SSL
I'll look into this and get back to you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872541 Title: MySQL client fails to connect, seems to force SSL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1872541/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864958] Re: package mysql-server-8.0 8.0.19-0ubuntu0.19.10.3 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1
Another possible cause would be files being manually deleted from the datadir (so metadata tables believe they should still be there). Are the tables mentioned in the error log present and in use for the 5.7 packages? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864958 Title: package mysql-server-8.0 8.0.19-0ubuntu0.19.10.3 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1864958/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864958] Re: package mysql-server-8.0 8.0.19-0ubuntu0.19.10.3 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1
One more thing to try (pre-upgrade) is to download mysql-shell from https://dev.mysql.com/downloads/shell/ and run the upgrade checker utility, which has tests for common upgrade issues (https://dev.mysql.com/doc/mysql-shell/8.0/en/mysql-shell-utilities- upgrade.html) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864958 Title: package mysql-server-8.0 8.0.19-0ubuntu0.19.10.3 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1864958/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864958] Re: package mysql-server-8.0 8.0.19-0ubuntu0.19.10.3 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1
I can only remember seeing this once before, which was someone who had accidentally gone from 5.7 to 8.0, then back again to 5.7. Could you try running the mysqlcheck utility? Syntax would be something like «sudo mysqlcheck IP_PHONES» I think. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864958 Title: package mysql-server-8.0 8.0.19-0ubuntu0.19.10.3 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1864958/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864958] Re: package mysql-server-8.0 8.0.19-0ubuntu0.19.10.3 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1
Er, mysqlcheck only works if the server is running, so probably not very helpful. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864958 Title: package mysql-server-8.0 8.0.19-0ubuntu0.19.10.3 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1864958/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864958] Re: package mysql-server-8.0 8.0.19-0ubuntu0.19.10.3 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1
Before upgrading, could you ensure mysql_upgrade has been run on the 5.7 database (this should be automatic in ubuntu packaging unless you've copied older 5.7 files into a newer 5.7 installation)? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864958 Title: package mysql-server-8.0 8.0.19-0ubuntu0.19.10.3 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1864958/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1863318] Re: package mysql-server-5.7 5.7.29-0ubuntu0.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Hi, Thanks for the tip! This logic has changed significantly in Ubuntu 18+ to use new MySQL functionality to make the upgrade process more robust (using a method of starting the server that doesn't continue until it's ready for connections). 20.04 has MySQL 8.0, which has deprecated mysql_upgrade (upgrades are handled automatically by the server). Any waiting period would be an unreliable fix (some people would need longer wait still, and for everyone else it becomes an annoying delay), and I'm not sure it would be doable to backport major changes in the maintainer scripts to Ubuntu 16. -- Lars On 20/02/2020 14:49, Hans Rakers wrote: > I just ran into this same issue with 5.7.29-0ubuntu0.16.04.1. It is > caused by a race condition. > > It is a rather large MySQL database, so stopping & starting up the > daemon takes some time. Tried 'apt-get -f install' multiple times to no > avail. > > After going over the code in /var/lib/dpkg/info/mysql- > server-5.7.postinst, i managed to "fix" it by adding a 'sleep 5' at line > 317. Sleep 3 didn't cut it, it had to be sleep 5 :D > > Like so: > > if ! test_sysmaint_access; then >invoke stop >set_mysql_pw "debian-sys-maint" "$pass" >invoke start >echo "sleeping 5 secs" >sleep 5 > fi > # mysql_upgrade returns exit status 2 if the database is already upgraded > # (LP: #1566406) so ignore its exit status if it is 2. > result=0 > mysql_upgrade --defaults-file=/etc/mysql/debian.cnf || result=$? > > The way to finally get rid of these issues is to add something in this > script to check if the instance is ready for connections before starting > mysql_upgrade. > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863318 Title: package mysql-server-5.7 5.7.29-0ubuntu0.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1863318/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1858354] Re: /usr/sbin/mysqld:11:__gnu_cxx::new_allocator:__gnu_cxx::__alloc_traits:std::vector:sys_var::register_option:sys_var_add_options
It's not obvious just from the header what the cause is, so I've asked for access to get a stacktrace. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1858354 Title: /usr/sbin/mysqld:11:__gnu_cxx::new_allocator:__gnu_cxx::__alloc_traits:std::vector:sys_var::register_option:sys_var_add_options To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1858354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857584] Re: MySQL X protocol port 33060 listening on network by default
bind-address and mysqlx-bind-address both default to *, but the config file (/etc/mysql/mysql.conf.d/mysqld.cnf) sets bind-address to 127.0.0.1, so I think we just need to do the same for mysqlx-bind- address, as mentioned above. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1857584 Title: MySQL X protocol port 33060 listening on network by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1857584/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850895] Re: query_cache_limit removed in mysql-8, upgrade broke
*** This bug is a duplicate of bug 1612517 *** https://bugs.launchpad.net/bugs/1612517 Hi, Query cache support was removed in 8.0 (ref https://dev.mysql.com/doc/refman/8.0/en/mysql-nutshell.html and https://mysqlserverteam.com/mysql-8-0-retiring-support-for-the-query- cache/). Since these two options were in the 5.7 default config we do try to automatically handle it on upgrades, but the default config file location is /etc/mysql/mysql.conf.d/mysqld.cnf, so it only checks that location (/etc/mysql/my.cnf is also used by MariaDB, so by default it just includes the directory for the currently installed variant). The fix for this should simply be to comment out the two lines with query_cache, but if you receive any similar errors after doing that you can check the mysql-nutshell page linked above to see if there's been any change for it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850895 Title: query_cache_limit removed in mysql-8, upgrade broke To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1850895/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1658233] Re: missing apparmor rules
I think I have most of these fixed now, but am a bit confused about the org.freedesktop.systemd1 one, as it seems to come from usr/bin/dbus- daemon and not usr/sbin/mysqld? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1658233 Title: missing apparmor rules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1658233/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1795310] Re: FTBFS with MySQL 8.0
Sounds good :) The plan is to transition Ubuntu to 8.0 for 19.04, so hopefully this will propagate down before then. One note: Via https://bugs.launchpad.net/ubuntu/+source/pdns/+bug/1795336 I got an indication that what I said about it being backwards compatible isn't entirely correct. They had a build failure with MariaDB when switching to bool. I tested with int and a couple of packages building against MySQL 5.7, so it might just be that int is fine and bool isn't. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1795310 Title: FTBFS with MySQL 8.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freeradius/+bug/1795310/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1795336] Re: FTBFS with MySQL 8.0
Hm, but I see it's referenced as causing a build failure with MariaDB without also checking the MariaDB flag, so maybe there are issues with the older versions (I tested briefly with 5.7) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1795336 Title: FTBFS with MySQL 8.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pdns/+bug/1795336/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1795336] Re: FTBFS with MySQL 8.0
Actually, it should be backwards compatible. In 5.x, my_bool is typedef'ed to char, but functions using it will still happily accept int or bool (and most of the code I see in Ubuntu assigns it as one of those). Also, if it were not backwards-compatible, I don't think the upstream patch would work with MariaDB, since I believe «#if MYSQL_VERSION_ID >= 8» would be true. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1795336 Title: FTBFS with MySQL 8.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pdns/+bug/1795336/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1795364] [NEW] FTBFS with MySQL 8.0
Public bug reported: MySQL 8.0 removes the my_bool symbol, and it should simply be replaced with int or bool (this is also backwards-compatible with older versions of MySQL) ** Affects: vtk6 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1795364 Title: FTBFS with MySQL 8.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vtk6/+bug/1795364/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1795366] [NEW] FTBFS with MySQL 8.0
Public bug reported: MySQL 8.0 removes the my_bool symbol, and it should simply be replaced with int or bool (this is also backwards-compatible with older versions of MySQL) ** Affects: zabbix (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1795366 Title: FTBFS with MySQL 8.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zabbix/+bug/1795366/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1795365] [NEW] FTBFS with MySQL 8.0
Public bug reported: MySQL 8.0 removes the my_bool symbol, and it should simply be replaced with int or bool (this is also backwards-compatible with older versions of MySQL) ** Affects: w1retap (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1795365 Title: FTBFS with MySQL 8.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/w1retap/+bug/1795365/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1795359] [NEW] FTBFS with MySQL 8.0
Public bug reported: MySQL 8.0 removes the my_bool symbol, and it should simply be replaced with int or bool (this is also backwards-compatible with older versions of MySQL) ** Affects: redland (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1795359 Title: FTBFS with MySQL 8.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/redland/+bug/1795359/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1795363] [NEW] FTBFS with MySQL 8.0
Public bug reported: MySQL 8.0 removes the my_bool symbol, and it should simply be replaced with int or bool (this is also backwards-compatible with older versions of MySQL) ** Affects: ulogd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1795363 Title: FTBFS with MySQL 8.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ulogd/+bug/1795363/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1795358] [NEW] FTBFS with MySQL 8.0
Public bug reported: MySQL 8.0 removes the my_bool symbol, and it should simply be replaced with int or bool (this is also backwards-compatible with older versions of MySQL) ** Affects: qtbase-opensource-src (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1795358 Title: FTBFS with MySQL 8.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1795358/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1795361] [NEW] FTBFS with MySQL 8.0
Public bug reported: MySQL 8.0 removes the my_bool symbol, and it should simply be replaced with int or bool (this is also backwards-compatible with older versions of MySQL) ** Affects: tntdb (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1795361 Title: FTBFS with MySQL 8.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tntdb/+bug/1795361/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1795360] [NEW] FTBFS with MySQL 8.0
Public bug reported: MySQL 8.0 removes the my_bool symbol, and it should simply be replaced with int or bool (this is also backwards-compatible with older versions of MySQL) ** Affects: rmysql (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1795360 Title: FTBFS with MySQL 8.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rmysql/+bug/1795360/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1795362] [NEW] FTBFS with MySQL 8.0
Public bug reported: MySQL 8.0 removes the my_bool symbol, and it should simply be replaced with int or bool (this is also backwards-compatible with older versions of MySQL) ** Affects: trafficserver (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1795362 Title: FTBFS with MySQL 8.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/trafficserver/+bug/1795362/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1795356] [NEW] FTBFS with MySQL 8.0
Public bug reported: The my_config.h file is removed in MySQL 8.0. The include line can simply be removed, as mysql.h should be all that's needed. ** Affects: python-mysqldb (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1795356 Title: FTBFS with MySQL 8.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-mysqldb/+bug/1795356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1795354] [NEW] FTBFS with MySQL 8.0
Public bug reported: MySQL 8.0 removes the my_bool symbol, and it should simply be replaced with int or bool (this is also backwards-compatible with older versions of MySQL) ** Affects: proftpd-dfsg (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1795354 Title: FTBFS with MySQL 8.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/proftpd-dfsg/+bug/1795354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1795357] [NEW] FTBFS with MySQL 8.0
Public bug reported: MySQL 8.0 removes the my_bool symbol, and it should simply be replaced with int or bool (this is also backwards-compatible with older versions of MySQL) ** Affects: qt4-x11 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1795357 Title: FTBFS with MySQL 8.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/1795357/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1795350] [NEW] FTBFS with MySQL 8.0
Public bug reported: MySQL 8.0 removes the my_bool symbol, and it should simply be replaced with int or bool (this is also backwards-compatible with older versions of MySQL) ** Affects: poco (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1795350 Title: FTBFS with MySQL 8.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poco/+bug/1795350/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1795337] [NEW] FTBFS with MySQL 8.0
Public bug reported: MySQL 8.0 removes the my_bool symbol, and it should simply be replaced with int or bool (this is also backwards-compatible with older versions of MySQL) ** Affects: pike7.8 (Ubuntu) Importance: Undecided Status: New ** Affects: pike8.0 (Ubuntu) Importance: Undecided Status: New ** Also affects: pike7.8 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1795337 Title: FTBFS with MySQL 8.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pike7.8/+bug/1795337/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1795336] [NEW] FTBFS with MySQL 8.0
Public bug reported: MySQL 8.0 removes the my_bool symbol, and it should simply be replaced with int or bool (this is also backwards-compatible with older versions of MySQL) ** Affects: pdns (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1795336 Title: FTBFS with MySQL 8.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pdns/+bug/1795336/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1783502] Re: FTBFS with MySQL 8.0
Switching my_bool with int should actually be backwards-compatible, so the earlier patch can be simplified. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1783502 Title: FTBFS with MySQL 8.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mythtv/+bug/1783502/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1795333] [NEW] FTBFS with MySQL 8.0
Public bug reported: MySQL 8.0 removes the my_bool symbol, and it should simply be replaced with int or bool (this is also backwards-compatible with older versions of MySQL) Also, my_global.h and my_sys.h have been removed. Only mysql.h is needed. ** Affects: net-snmp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1795333 Title: FTBFS with MySQL 8.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/net-snmp/+bug/1795333/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1795334] [NEW] FTBFS with MySQL 8.0
Public bug reported: MySQL 8.0 removes the my_bool symbol, and it should simply be replaced with int or bool (this is also backwards-compatible with older versions of MySQL) ** Affects: opendnssec (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1795334 Title: FTBFS with MySQL 8.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opendnssec/+bug/1795334/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1795335] [NEW] FTBFS with MySQL 8.0
Public bug reported: MySQL 8.0 removes the my_bool symbol, and it should simply be replaced with int or bool (this is also backwards-compatible with older versions of MySQL) ** Affects: opensips (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1795335 Title: FTBFS with MySQL 8.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opensips/+bug/1795335/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1795331] [NEW] FTBFS with MySQL 8.0
Public bug reported: The package uses a couple of symbols that have been removed in MySQL 8.0: MYSQL_OPT_SSL_VERIFY_SERVER_CERT MYSQL_SECURE_AUTH Additionally, MySQL 8.0 removes the my_bool type, and it should simply be replaced with int or bool (this is also backwards-compatible with older versions of MySQL) ** Affects: mysql-ocaml (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1795331 Title: FTBFS with MySQL 8.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-ocaml/+bug/1795331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1795327] [NEW] FTBFS with MySQL 8.0
Public bug reported: MySQL 8.0 removes the my_bool symbol, and it should simply be replaced with int or bool (this is also backwards-compatible with older versions of MySQL) ** Affects: lighttpd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1795327 Title: FTBFS with MySQL 8.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lighttpd/+bug/1795327/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1795329] [NEW] FTBFS with MySQL 8.0
Public bug reported: The package uses a number of symbols that have been removed in MySQL 8.0 The list includes: MYSQL_OPT_GUESS_CONNECTION MYSQL_SECURE_AUTH MYSQL_SET_CLIENT_IP MYSQL_OPT_USE_EMBEDDED_CONNECTION MYSQL_OPT_USE_REMOTE_CONNECTION ** Affects: mysql++ (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1795329 Title: FTBFS with MySQL 8.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql++/+bug/1795329/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1795328] [NEW] FTBFS with MySQL 8.0
Public bug reported: MySQL 8.0 removes the my_bool symbol, and it should simply be replaced with int or bool (this is also backwards-compatible with older versions of MySQL) ** Affects: lua-dbi (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1795328 Title: FTBFS with MySQL 8.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lua-dbi/+bug/1795328/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1795326] [NEW] FTBFS with MySQL 8.0
Public bug reported: The MYSQL_SECURE_AUTH symbol was deprecated in MySQL 5.7 and removed in 8.0. Additionally, MySQL 8.0 removes the my_bool symbol, and it should simply be replaced with int or bool (this is also backwards-compatible with older versions of MySQL) ** Affects: libzdb (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1795326 Title: FTBFS with MySQL 8.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libzdb/+bug/1795326/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1795322] [NEW] FTBFS with MySQL 8.0
Public bug reported: MySQL 8.0 removes the my_bool symbol, and it should simply be replaced with int or bool (this is also backwards-compatible with older versions of MySQL) ** Affects: libgda5 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1795322 Title: FTBFS with MySQL 8.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libgda5/+bug/1795322/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1795323] [NEW] FTBFS with MySQL 8.0
Public bug reported: MySQL 8.0 removes the my_bool symbol, and it should simply be replaced with int or bool (this is also backwards-compatible with older versions of MySQL) ** Affects: libodb-mysql (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1795323 Title: FTBFS with MySQL 8.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libodb-mysql/+bug/1795323/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1795321] [NEW] FTBFS with MySQL 8.0
Public bug reported: Package testing tries to run mysql_install_db, which has been deprecated since 5.7 and removed in 8.0. Should switch to using mysqld --initialize (5.7 also changed the flags for mysql_install_db, so it should simply be a matter to switching the command for 5.7+) ** Affects: libdbi-drivers (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1795321 Title: FTBFS with MySQL 8.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdbi-drivers/+bug/1795321/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1795315] [NEW] FTBFS with MySQL 8.0
Public bug reported: MySQL 8.0 removes the my_bool symbol, and it should simply be replaced with int or bool (this is also backwards-compatible with older versions of MySQL) ** Affects: kamailio (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1795315 Title: FTBFS with MySQL 8.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kamailio/+bug/1795315/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1795317] [NEW] FTBFS with MySQL 8.0
Public bug reported: MySQL 8.0 removes the my_bool symbol, and it should simply be replaced with int or bool (this is also backwards-compatible with older versions of MySQL) ** Affects: kannel (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1795317 Title: FTBFS with MySQL 8.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kannel/+bug/1795317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1795318] [NEW] FTBFS with MySQL 8.0
Public bug reported: MySQL 8.0 removes the my_bool symbol, and it should simply be replaced with int or bool (this is also backwards-compatible with older versions of MySQL) ** Affects: kdb (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1795318 Title: FTBFS with MySQL 8.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdb/+bug/1795318/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1795319] [NEW] FTBFS with MySQL 8.0
Public bug reported: MySQL 8.0 removes the my_bool symbol, and it should simply be replaced with int or bool (this is also backwards-compatible with older versions of MySQL) ** Affects: kopanocore (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1795319 Title: FTBFS with MySQL 8.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kopanocore/+bug/1795319/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1795308] [NEW] FTBFS with MySQL 8.0
Public bug reported: MySQL 8.0 removes the my_bool symbol, and it should simply be replaced with int or bool (this is also backwards-compatible with older versions of MySQL) ** Affects: cppdb (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1795308 Title: FTBFS with MySQL 8.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cppdb/+bug/1795308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1795314] [NEW] FTBFS with MySQL 8.0
Public bug reported: MySQL 8.0 removes the my_bool symbol, and it should simply be replaced with int or bool (this is also backwards-compatible with older versions of MySQL) ** Affects: isc-kea (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1795314 Title: FTBFS with MySQL 8.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-kea/+bug/1795314/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1795310] [NEW] FTBFS with MySQL 8.0
Public bug reported: MySQL 8.0 removes the my_bool symbol, and it should simply be replaced with int or bool (this is also backwards-compatible with older versions of MySQL) ** Affects: freeradius (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1795310 Title: FTBFS with MySQL 8.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freeradius/+bug/1795310/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1795312] [NEW] FTBFS with MySQL 8.0
Public bug reported: MySQL 8.0 removes the my_bool symbol, and it should simply be replaced with int or bool (this is also backwards-compatible with older versions of MySQL) ** Affects: gnokii (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1795312 Title: FTBFS with MySQL 8.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnokii/+bug/1795312/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1795304] [NEW] FTBFS with MySQL 8.0
Public bug reported: MySQL 8.0 removes the my_bool symbol, and it should simply be replaced with int or bool (this is also backwards-compatible with older versions of MySQL) ** Affects: asterisk (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1795304 Title: FTBFS with MySQL 8.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/asterisk/+bug/1795304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1795306] [NEW] FTBFS with MySQL 8.0
Public bug reported: MySQL 8.0 removes the my_bool symbol, and it should simply be replaced with int or bool (this is also backwards-compatible with older versions of MySQL) ** Affects: bacula (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1795306 Title: FTBFS with MySQL 8.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bacula/+bug/1795306/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1795303] [NEW] FTBFS with MySQL 8.0
Public bug reported: MySQL 8.0 removes the my_bool symbol, and it should simply be replaced with int or bool (this is also backwards-compatible with older versions of MySQL) ** Affects: argus-clients (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1795303 Title: FTBFS with MySQL 8.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/argus-clients/+bug/1795303/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1792542] [NEW] FTBFS with MySQL 8.0
Public bug reported: The my_bool type has been removed in 8.0, and should be replaced with bool (requires c++ or c99) or int. ** Affects: apr-util (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1792542 Title: FTBFS with MySQL 8.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apr-util/+bug/1792542/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1792535] Re: FTBFS with MySQL 8.0
The attached patch simply removes the two include lines ** Patch added: "Quilt patch" https://bugs.launchpad.net/ubuntu/+source/apophenia/+bug/1792535/+attachment/5188724/+files/mysql-8.0.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1792535 Title: FTBFS with MySQL 8.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apophenia/+bug/1792535/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1792535] [NEW] FTBFS with MySQL 8.0
Public bug reported: The build fails because the code attempts to include two header files that are removed in 8.0: my_global.h and my_sys.h The includes can simply be removed; Including mysql.h is all that's needed. Note that this is also the case for MySQL 5.7, so the patch won't break 5.7 builds ** Affects: apophenia (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1792535 Title: FTBFS with MySQL 8.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apophenia/+bug/1792535/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1791010] Re: 128 bit float precision breaks mysql self-tests (stalls cosmic updates)
On 12. sep. 2018 07:08, Christian Ehrhardt wrote: > Your upload seems to build fine on all architectures and checking ppc64 > in particular the tests that formerly failed are good now. > >The servers were restarted 167 times >Spent 1178.435 of 482 seconds executing testcases >Completed: All 768 tests were successful. >157 tests were skipped, 59 by the test itself. > > That said I thought this looks good and you could go on coordinating with > rbasak and tsimonq (who synced the last version) for the upload into cosmic > that should finally unblock it from proposed migration. > But I realized that the build log in the PPA still has: > Depends: [...] libmecab2 > which should also be removed for 18.10 as the security review isn't complete > and we have a component mismatch at the moment (the synced version currently > in cosmic-proposed blocks on the lack of mecab in main). > Right, we have a routine for dropping the mecab dependency from Ubuntu. I'll add the patch descriptions etc. and prepare the upload :) -- Lars -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1791010 Title: 128 bit float precision breaks mysql self-tests (stalls cosmic updates) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1791010/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1791010] Re: 128 bit float precision breaks mysql self-tests (stalls cosmic updates)
Made a test patch and uploaded to https://launchpad.net/~mysql- ubuntu/+archive/ubuntu/mysql-5.7/+packages (also set test failures to break the build on all architectures, rather than just i386 and amd64) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1791010 Title: 128 bit float precision breaks mysql self-tests (stalls cosmic updates) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1791010/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1791018] Re: self-test errors do not break the build
I did a test at https://launchpad.net/~mysql- ubuntu/+archive/ubuntu/mysql-5.7/+packages by enforcing the test suite on all architectures, and it's actually green. Was going to suggest we enable it for arm64, but maybe we should consider the rest as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1791018 Title: self-test errors do not break the build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1791018/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1791018] Re: self-test errors do not break the build
During build, passing the mtr suite is only enforced for i386 and amd64 architectures, because upstream has limited support for others, so the test suites tended to be unstable or failing "reliably" (particularly due to floating point differences as in this case). We actually release arm64 packages for 8.0 now, and fixing tests there also made the situation better on pcc64el, which might have made it temporarily green for autopkgtest only to have it regress again since it receives very little upstream testing. Previously, autopkgtest for ppc64el was marked as expected failure -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1791018 Title: self-test errors do not break the build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1791018/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1783931] Re: Post ubuntu installation with LAMP default databases are not being created
Hi, This is expected, yes, and was changed from 5.6 to 5.7. Test schema was removed because it was a potential security issue (https://blogs.oracle.com/jsmyth/the-test-database-and-security) More can be seen about the sys schema here https://dev.mysql.com/doc/refman/5.7/en/sys-schema.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1783931 Title: Post ubuntu installation with LAMP default databases are not being created To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1783931/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1783502] Re: FTBFS with MySQL 8.0
Patch uses int if the MySQL version is 8.0 or greater, otherwise my_bool. ** Patch added: "mysql-8.0.patch" https://bugs.launchpad.net/ubuntu/+source/mythtv/+bug/1783502/+attachment/5167497/+files/mysql-8.0.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1783502 Title: FTBFS with MySQL 8.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mythtv/+bug/1783502/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1783502] Re: FTBFS with MySQL 8.0
Upstream bug report: https://code.mythtv.org/trac/ticket/13304 ** Bug watch added: code.mythtv.org/trac/ #13304 http://code.mythtv.org/trac/ticket/13304 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1783502 Title: FTBFS with MySQL 8.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mythtv/+bug/1783502/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1783502] [NEW] FTBFS with MySQL 8.0
Public bug reported: Build fails because the my_bool type has been removed in MySQL, to be replaced with either int or bool (ref: https://dev.mysql.com/doc/refman/8.0/en/c-api-data-structures.html) ** Affects: mythtv (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1783502 Title: FTBFS with MySQL 8.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mythtv/+bug/1783502/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1781529] [NEW] [MIR] mecab
Public bug reported: Note: Both mecab and MySQL have a dependency on mecab-ipadic, so the request is for both mecab and mecab-ipadic [Availability] mecab and mecab-ipadic are in universe/misc (they are part of the same piece of software with upstream source https://github.com/taku910/mecab, but separate source packages) [Rationale] Mecab is used by MySQL for Japanese text parsing (https://dev.mysql.com/doc/refman/8.0/en/fulltext-search-mecab.html), and is a build-dependency for Upstream/Debian MySQL packages. Since it is currently in universe, we maintain a diff for Ubuntu that removes this dependency (also removing the plugin). Including mecab and mecab-ipadic in main would let us include the text parsing features and allow us to drop the diff between Debian and Ubuntu for MySQL. The package is a simple language parsing tool that has very few changes (but packaging is kept up to date by the mantainers). [Security] - Only found CVE was http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-3231 (affecting versions older than 0.96). This was patched in 0.95 package before version update. - No security relevant binaries [Quality assurance] - The packages are very simple, being just simple text parser util and csv files. - Only outstanding bug is https://bugs.launchpad.net/ubuntu/+source/mecab/+bug/1469406 - Package itself hasn't changed since 2013, but packaging is kept up-to-date by maintainers - Package is missing d/watch and|or d/README.source [Dependencies] mecab depends on mecab-ipadic. Other dependencies are in main [Standards compliance] No issues reported by lintian, and package is synced directly from Debian. [Maintenance] Both packages are maintained by Natural Language Processing (Japanese) Last few years have had little maintainer work except for keeping packaging up-to-date (new standards versions, vcs urls etc.). [Background information] - The mecab package provides Japanese text parsing (through library or stdin interface) - mecab-ipadic is an international phonetic alphabet (ipa) dictionary for mecab ** Affects: mecab (Ubuntu) Importance: Undecided Status: New ** Affects: mecab-ipadic (Ubuntu) Importance: Undecided Status: New ** Also affects: mecab-ipadic (Ubuntu) Importance: Undecided Status: New ** Description changed: Note: Both mecab and MySQL have a dependency on mecab-ipadic, so the request is for both mecab and mecab-ipadic [Availability] - mecab and mecab-ipadic are in universe/misc (they are part of the same piece of software with upstream source https://github.com/taku910/mecab, but separate source packages) + + mecab and mecab-ipadic are in universe/misc (they are part of the same + piece of software with upstream source https://github.com/taku910/mecab, + but separate source packages) [Rationale] + Mecab is used by MySQL for Japanese text parsing (https://dev.mysql.com/doc/refman/8.0/en/fulltext-search-mecab.html), and is a build-dependency for Upstream/Debian MySQL packages. Since it is currently in universe, we maintain a diff for Ubuntu that removes this dependency (also removing the plugin). Including mecab and mecab-ipadic in main would let us include the text parsing features and allow us to drop the diff between Debian and Ubuntu for MySQL. The package is a simple language parsing tool that has very few changes (but packaging is kept up to date by the mantainers). [Security] - Only found CVE was http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-3231 (affecting versions older than 0.96). This was patched in 0.95 package before version update. - No security relevant binaries [Quality assurance] - - Packages are very simple, being just simple text parser util and csv files. + + - The packages are very simple, being just simple text parser util and csv files. - Only outstanding bug is https://bugs.launchpad.net/ubuntu/+source/mecab/+bug/1469406 - Package itself hasn't changed since 2013, but packaging is kept up-to-date by maintainers - Package is missing d/watch and|or d/README.source [Dependencies] + mecab depends on mecab-ipadic. Other dependencies are in main [Standards compliance] - No issues reported by lintian, and package is synced directly from Debian. + + No issues reported by lintian, and package is synced directly from + Debian. [Maintenance] Both packages are maintained by Natural Language Processing (Japanese) Last few years have had little maintainer work except for keeping packaging up-to-date (new standards versions, vcs urls etc.). [Background information] + - The mecab package provides Japanese text parsing (through library or stdin interface) - mecab-ipadic is an international phonetic alphabet (ipa) dictionary for mecab -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1781529 Title:
[Bug 1563274] Re: dbconfig-mysql sets blank port in config
5.7.22 (in Ubuntu 16.04) still supports the empty port value, so I don't think the issue is really related to this. The "empty value specified" message is basically a deprecation warning in 5.7, but changed to error in 8.0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1563274 Title: dbconfig-mysql sets blank port in config To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbconfig-common/+bug/1563274/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
