27;re looking for is
http://bazaar.launchpad.net/~mysql/mysql-server/5.7/revision/4532#sql/log_event.cc.
I haven't verified that it really is bug #65551 you're experiencing, but
if you are, that patch should fix it.
Regards,
Norvald H. Ryeng
--
To UNSUBSCRIBE, email to debian-bugs-d
704286. The fix
introduced a check to handle kill signals for long running
queries but the cursor was not restored to the proper state."
Regards,
Norvald H. Ryeng
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe&q
forwarded 712730 http://bugs.mysql.com/bug.php?id=69374
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
This bug is fixed in MySQL 5.1.70, 5.5.32 and 5.6.12, cf. the July CPU.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
ething out.
Regards,
Norvald H. Ryeng
Thanks for the strace and logs!
It looks very much like the OS is refusing the MySQL daemon access to
the config file and datadir, even though the user can read them. Are
you perhaps using SELinux or apparmor? If you are, dmesg should tell
you what's going on.
Regards,
Norvald H. Ryeng
Vulnerabilities fixed by upgrading from 5.5.47 to 5.5.49:
CVE-2016-0640
CVE-2016-0641
CVE-2016-0642
CVE-2016-0643
CVE-2016-0644
CVE-2016-0646
CVE-2016-0647
CVE-2016-0648
CVE-2016-0649
CVE-2016-0650
CVE-2016-0666
CVE-2016-2047
Vulnerabilities fixed by upgrading from 5.6.28 to 5.6.30:
CVE-2015-3194
CVE-2016-0639
CVE-2016-0640
CVE-2016-0641
CVE-2016-0642
CVE-2016-0643
CVE-2016-0644
CVE-2016-0646
CVE-2016-0647
CVE-2016-0648
CVE-2016-0649
CVE-2016-0650
CVE-2016-0655
CVE-2016-0661
CVE-2016-0665
CVE-2016-0666
CVE-2016-0668
C
decide if it's needed or not.
More people are going to encounter this when upgrading to jessie if they
haven't upgraded their MySQL for a long time.
The same behavior is there in wheezy, so it shouldn't come as a surprise
in jessie.
Regards,
Norvald H. Ryeng
--
To UNSUBSCR
On Tue, 10 Feb 2015 13:56:20 +0100, Daniel Pocock
wrote:
On 10/02/15 13:46, Norvald H. Ryeng wrote:
On Tue, 10 Feb 2015 09:37:28 +0100, Daniel Pocock
wrote:
What is the status of this bug?
The status is "forwarded", which means it's been forwarded to
upstream. Upstream h
also applies to mysql-5.5 and mariadb-10
That shouldn't be a problem as long as they use /bin/bash. But I won't
mind if you get rid of the bashisms and convert them to /bin/sh.
Regards,
Norvald H. Ryeng
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a
bash specific syntax (bashisms) in scripts
run with /bin/sh. If you use /bin/bash, you can use all the bashisms you
want.
Of course, sticking to strict POSIX sh is generally a good thing, but I
think we have more important things to work on just now.
Regards,
Norvald H. Ryeng
--
To UNSUBS
Package: release-notes
Section 2.2.5 in the jessie release notes states that MySQL 5.5 support
ends in December 2017, but extended support lasts until December 2018 [1],
and that includes bug fixes [2]. So patches should be coming until at
least December 2018.
Regards,
Norvald H. Ryeng
;m poking people upstream to
increase priority and speed things up a bit.
Regards,
Norvald H. Ryeng
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
On Fri, 20 Feb 2015 10:28:19 +0100, Jan Wagner wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi Norvald,
Am 20.02.2015 um 09:01 schrieb Norvald H. Ryeng:
Because of the new my.cnf setup (splitting MySQL, MariaDB and
Percona), it should include /etc/mysql/mysql.conf.d/, too. The
m. The MariaDB packages have put options in
/etc/mysql/my.cnf that are not valid MySQL options, so the MySQL server
will refuse to start. An apt-get purge of MariaDB packages before trying
to install MySQL should fix it.
Regards,
Norvald H. Ryeng
I've forwarded the bug to upstream: http://bugs.mysql.com/bug.php?id=77447
A similar change has already been applied to MySQL 5.6, so the issue may
simply disappear when we upgrade.
Regards,
Norvald H. Ryeng
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
w
Hi Ulric,
Could this be the same bug as https://bugs.mysql.com/bug.php?id=79185?
In any case, this looks like an issue that should be reported and fixed
upstream. If you could provide a way to reproduce the bug, that would be
very much appreciated.
Regards,
Norvald H. Ryeng
#x27;t take extremely large
files. If you limit logs to roughly the relevant parts, it's also easier
to read. :-)
Regards,
Norvald H. Ryeng
you please give reasoning, thank you.
This issue was fixed as CVE-2013-0375 in MySQL 5.1.67 and 5.5.29 [1].
CVE-2013-0375 and CVE-2012-4414 are equivalent.
Regards,
Norvald H. Ryeng
[1]
http://www.oracle.com/technetwork/topics/security/cpujan2013-1515902.html#AppendixMSQL
--
To
5.5.47.
The CVE numbers will be available when the CPU is released.
All necessary work to upgrade to 5.5.47 has already been done in git.
Someone just needs to tag it and upload.
Regards,
Norvald H. Ryeng
[1]
http://www.oracle.com/technetwork/topics/security/cpujan2016-2367955.html
.
The CVE numbers will be available when the CPU is released.
Regards,
Norvald H. Ryeng
[1]
http://www.oracle.com/technetwork/topics/security/cpujan2016-2367955.html
CVE-2016-0609
CVE-2016-0596
CVE-2016-0503
CVE-2016-0504
CVE-2016-0607
CVE-2016-0611
CVE-2016-0595
CVE-2016-0610
Regards,
Norvald H. Ryeng
CVE-2016-0609
CVE-2016-0596
CVE-2016-0616
Regards,
Norvald H. Ryeng
.6 is arriving in the archives soon, and when it does, amarok must
be changed to link to libmysqld.a and depend on the libmysqld-dev package.
Regards,
Norvald H. Ryeng
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble?
t any DDs around. Could you help us out with
this upload, please?
Best regards,
Norvald H. Ryeng
.
The CVE numbers will be available when the CPU is released.
Please note that the MySQL release cycle has changed from every two
months to every three months. The releases are now synchronized with
the CPU announcements.
Best regards,
Norvald H. Ryeng
[1] http://www.oracle.com/technetwork
CVE numbers will be available when the CPU is released.
Please note that the MySQL release cycle has changed from every two
months to every three months. The releases are now synchronized with
the CPU announcements.
Best regards,
Norvald H. Ryeng
[1] http://www.oracle.com/technetwork/security
regards,
Norvald H. Ryeng
mysql_config and mysqlclient.pc pick up compile flags from the build
environment. We have a fix for this upstream, and I've backported it to
5.7.16 (see attachment).
I haven't tested it with sbuild/dpkg, so when applying this, please
verify that mysql_config and mysqlclient.pc don't pick up any fl
tps://www.percona.com/forums/questions-discussions/mysql-and-percona-server/12516-mysql_upgrade-failing-on-5-5-to-5-6-in-place-upgrade
Regards,
Norvald H. Ryeng
On Sat, 26 Nov 2016 00:00:53 +0800
積丹尼 Dan Jacobson wrote:
> NHR> SELECT * FROM mysql.user WHERE LENGTH(password) = 16;
>
> ERROR 1054 (42S22) at line 1: Unknown column 'password' in 'where
> clause'
>
> in fact there is only
>
> Host User Select_priv Insert_priv Update_priv Delete_priv Crea
those users,
e.g., "mysql_native_password".
Please read http://dev.mysql.com/doc/refman/5.7/en/alter-user.html for
details about the ALTER USER command.
Regards,
Norvald H. Ryeng
nst our will, and despite our
huge effort to make MySQL and MariaDB coexist and our efforts to
fulfill all demands from the release and security teams.
Regards,
Norvald H. Ryeng
5.5.54.
The CVE numbers will be available when the CPU is released.
Regards,
Norvald H. Ryeng
[1] http://www.oracle.com/technetwork/security-advisory/cpujan2017-2881727.html
.
The CVE numbers will be available when the CPU is released.
Regards,
Norvald H. Ryeng
[1] http://www.oracle.com/technetwork/security-advisory/cpujan2017-2881727.html
.
The CVE numbers will be available when the CPU is released.
Regards,
Norvald H. Ryeng
[1] http://www.oracle.com/technetwork/security-advisory/cpujan2017-2881727.html
On Thu, 12 Jan 2017 22:38:19 +0100
Kristian Nielsen wrote:
> "Norvald H. Ryeng" writes:
> > The transition is being executed by the release team and the MariaDB
> > maintainers. Please keep the MySQL maintainers out of it. Our
> > packages are being removed fro
5.5.53.
The CVE numbers will be available when the CPU is released.
Regards,
Norvald H. Ryeng
[1]
http://www.oracle.com/technetwork/security-advisory/cpuoct2016-2881722.html
.
The CVE numbers will be available when the CPU is released.
Regards,
Norvald H. Ryeng
[1]
http://www.oracle.com/technetwork/security-advisory/cpuoct2016-2881722.html
.
The CVE numbers will be available when the CPU is released.
Regards,
Norvald H. Ryeng
[1]
http://www.oracle.com/technetwork/security-advisory/cpuoct2016-2881722.html
CVE numbers will be available when the CPU is released.
Regards,
Norvald H. Ryeng
[1]
http://www.oracle.com/technetwork/topics/security/cpuapr2016-2881694.html
.
The CVE numbers will be available when the CPU is released.
Regards,
Norvald H. Ryeng
[1]
http://www.oracle.com/technetwork/topics/security/cpuapr2016-2881694.html
CVE numbers will be available when the CPU is released.
Regards,
Norvald H. Ryeng
[1] http://www.oracle.com/technetwork/security-advisory/cpuoct2017-3236626.html
5.5.58.
The CVE numbers will be available when the CPU is released.
Regards,
Norvald H. Ryeng
[1] http://www.oracle.com/technetwork/security-advisory/cpuoct2017-3236626.html
45 matches
Mail list logo
