Am 08.05.2015 um 12:06 schrieb Sergei Golubchik:
Hi, Reindl!
On May 07, Reindl Harald wrote:
No, it affects the server, not mysql_upgrade. But it's a new
statement, that mysql_upgrade is using, no existing query can
possibly trigger that bug
well, in other words anybody could crash the s
Hi, Reindl!
On May 07, Reindl Harald wrote:
>
> > No, it affects the server, not mysql_upgrade. But it's a new
> > statement, that mysql_upgrade is using, no existing query can
> > possibly trigger that bug
>
> well, in other words anybody could crash the server by write a
> specific query and
Am 07.05.2015 um 23:45 schrieb Sergei Golubchik:
On May 07, Reindl Harald wrote:
and the Fedora 20 build is completly broken and crashs due "mysql_upgrade"
Yes, I've just fixed it. But too late for 10.0.18 :(
Your most simple workaround would be not to run mysql_upgrade. It
wouldn't do anyth
Hi, Reindl!
On May 07, Reindl Harald wrote:
>
> interesting - in fact it's -mtune=sandybridge versus -mtune=westmere
> while i am pretty sure that i rebuilt any local maintained packages
> recently for sandybrige to test because a hardware replacement is
> planned in august resulting in the ol
Hi, Reindl!
On May 07, Reindl Harald wrote:
> Am 07.05.2015 um 22:29 schrieb Sergei Golubchik:
> > On May 07, Reindl Harald wrote:
> >>
> >> Am 07.05.2015 um 21:02 schrieb Reindl Harald:
> >>> Don't build on Fedora 21 / gcc-4.9.2-6.fc21.x86_64 but on Fedora 20 /
> >>> gcc-4.8.3-7.fc20.x86_64 which
Am 07.05.2015 um 22:43 schrieb Sergei Golubchik:
Hi, Reindl!
On May 07, Reindl Harald wrote:
Am 07.05.2015 um 21:27 schrieb Sergei Golubchik:
Hi, Reindl!
On May 07, Reindl Harald wrote:
Don't build on Fedora 21 / gcc-4.9.2-6.fc21.x86_64 but on Fedora 20 /
gcc-4.8.3-7.fc20.x86_64 which is no
Am 07.05.2015 um 22:29 schrieb Sergei Golubchik:
Hi, Reindl!
On May 07, Reindl Harald wrote:
Am 07.05.2015 um 21:02 schrieb Reindl Harald:
Don't build on Fedora 21 / gcc-4.9.2-6.fc21.x86_64 but on Fedora 20 /
gcc-4.8.3-7.fc20.x86_64 which is not a good sign since 10.0.17 with
identical env
Hi, Reindl!
On May 07, Reindl Harald wrote:
> Am 07.05.2015 um 21:27 schrieb Sergei Golubchik:
> > Hi, Reindl!
> >
> > On May 07, Reindl Harald wrote:
> >> Don't build on Fedora 21 / gcc-4.9.2-6.fc21.x86_64 but on Fedora 20 /
> >> gcc-4.8.3-7.fc20.x86_64 which is not a good sign since 10.0.17 with
Hi, Reindl!
On May 07, Reindl Harald wrote:
>
>
> Am 07.05.2015 um 21:02 schrieb Reindl Harald:
> > Don't build on Fedora 21 / gcc-4.9.2-6.fc21.x86_64 but on Fedora 20 /
> > gcc-4.8.3-7.fc20.x86_64 which is not a good sign since 10.0.17 with
> > identical environment builds on both
>
> and the
Am 07.05.2015 um 21:27 schrieb Sergei Golubchik:
Hi, Reindl!
On May 07, Reindl Harald wrote:
Don't build on Fedora 21 / gcc-4.9.2-6.fc21.x86_64 but on Fedora 20 /
gcc-4.8.3-7.fc20.x86_64 which is not a good sign since 10.0.17 with
identical environment builds on both
This doesn't help much,
Hi, Reindl!
On May 07, Reindl Harald wrote:
> Don't build on Fedora 21 / gcc-4.9.2-6.fc21.x86_64 but on Fedora 20 /
> gcc-4.8.3-7.fc20.x86_64 which is not a good sign since 10.0.17 with
> identical environment builds on both
>
> Building C object strings/CMakeFiles/strings.dir/strxmov.c.o
> cd
Am 07.05.2015 um 21:02 schrieb Reindl Harald:
Don't build on Fedora 21 / gcc-4.9.2-6.fc21.x86_64 but on Fedora 20 /
gcc-4.8.3-7.fc20.x86_64 which is not a good sign since 10.0.17 with
identical environment builds on both
and the Fedora 20 build is completly broken and crashs due "mysql_upgrad
The MariaDB project is pleased to announce the immediate availability
of MariaDB 10.0.18. This is a Stable (GA) release. See the Release
Notes and Changelog for details.
- - Links - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
MariaDB 10.0.18
- Release Notes: https://mariadb.com/k
13 matches
Mail list logo
