Public bug reported:
MySQL 5.7 restricts which symbols are exported and useable from the
outside.
The function load_defaults, using in apps/snmptrapd_sql.c is not exported from
libmysqlclient20, so the build will fail.
However, the function my_load_defaults is exported, and has the same signatur
pitti: Yeah, we have a bug in dbconfig-common (1563274), and a patch
ready for mysql-5.7 that downgrades that error to a deprecation warning
to give them time to fix it
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
htt
As this isn't a simple fix, and is currently blocking MySQL 5.7 in
Ubuntu 16, we will patch MySQL to allow the empty port option for now
(it will print a warning instead of the error).
There's also a related upstream bug at
http://bugs.mysql.com/bug.php?id=80903
** Bug watch added: MySQL Bug Syst
** Also affects: mysql-5.7 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dbconfig-common in Ubuntu.
https://bugs.launchpad.net/bugs/1563274
Title:
dbconfig-mysql sets blank port
Yeah, the copying is an ugly hack, but it's already done to some degree,
and has the least risk of breaking anything, I think.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1528583
Titl
Public bug reported:
For non-remote setups, dbconfig will not set a port value, leaving it
blank in generated option files.
MySQL 5.7 will no longer accept a blank port option in the config file
(See https://github.com/mysql/mysql-
server/commit/3d8b4570d1a9d8d03d32e4cd6705b6a2d354e992 for more
i
The test failures for dbconfig-common and redmine are due to a) The
tests setting empty port options in config files and b) MySQL 5.7 no
longer allowing empty options in config file.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the b
Some of the headers that are in include/mysql/mysql are also copied (not
moved) to include/mysql, probably to patch this sort of problem. With
the way the headers are structured right now I don't really see a very
nice way to solve this, so one suggestion is to simply copy everything.
--
You rece
The previous comment contains the overview of the upgrade testing we've
done.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1528583
Title:
[FFe] Please update to MySQL 5.7 series
To
1 Background
These tests were conducted to verify that MySQL upgrades are possible
from from previous Ubuntu releases to Ubuntu 16.04 (Xenial Xerus).
There are 3 live Ubuntu versions:
- Ubuntu 12.04 LTS (Precise Pangolin)
- Ships with MySQL 5.5
- Ubuntu 14.04 LTS (Trusty Tahr)
I'll do a more complete writeup once the testing is complete, but want
to follow up on the above comment:
I can confirm that the package from ppa:racb/experimental fixes the apparmor
issue we saw before.
I've also tested the same starting from Precise.
So the upgrade from 5.5 in Trusty to 5.7 in
I'm a part of the MySQL engineering team, and have been working with
Robie Basak on this for a while
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1528583
Title:
[FFe] Please update t
I've redone the basic smoke testing for verifying just the package upgrades.
No issues were found during testing.
These tests do not include full Ubuntu release upgrades; They were only run on
16.04.
To include 5.5 I rebuilt it from the current 5.5.47 source in Debian. The 5.6
packages were used
I've been testing the packages as we work on them, ironing out issues with
upgrading from both 5.5 and 5.6 as we go (I'll need to rerun these tests for
the currently uploaded package, though).
But I've only been testing on Xenial, i.e. installing 5.5/5.6 then replacing
with 5.7, so I haven't don
Alternate amarok patch:
Changes it to depend on virtual-mysql-server-core instead of changing 5.7
packaging to provide mysql-server-core.
** Attachment added: "Alternative debdiff for amarok package"
https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1528583/+attachment/4578102/+files/a
The package libmysqld-pic has been removed as it is obsolete (there was
no difference between libmysqld-pic and libmysqld-dev in 5.6 either).
The amarok package depends on it, so this dependency needs changing.
Attaching debdiff output for the patch.
Another note is that it also depends on mysql-
Packaging has been moved to master branch of
https://github.com/ltangvald/mysql-5.7/
and uploaded to https://launchpad.net/~lars-tangvald/+archive/ubuntu/mysql-5.7
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.6 in Ubuntu
** Changed in: mysql-5.6 (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1528583
Title:
Please update to MySQL 5.7 series
To manage
I've uploaded the packaging to
https://github.com/ltangvald/mysql-5.7/tree/mysql-alt (will add to a ppa as
well).
Should be ready to start testing and reviewing.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.6 in Ubuntu.
htt
@Robie Yup, I'll post a patch for this
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1468185
Title:
Function 'innodb' already exists and other errors
To manage notifications ab
The cause is that MySQL used to only support implicit timestamp default
value, which is not according to the SQL spec. When this was fixed, it
was decided to keep the old behavior for historical reasons, but add a
deprecation warning.
Adding the suggested value to the config would remove the warni
Will try to get a patch for this up tomorrow. Note that it's not a
serious error, just output junk, so the workaround is basically to
ignore it :)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.6 in Ubuntu.
https://bugs.launchp
Yes, this seems to be something that was copied over from 5.5 and can be
removed.
--
Lars
On 11/18/2015 11:18 AM, 冯宇 wrote:
> +1 Same issue here.
>
> This might be ha_innodb.so and other files not exist in
> /usr/lib/mysql/plugin/, but mysql-server-5.5 contains these files.
>
--
You received t
23 matches
Mail list logo
