> Thinking about this some more, maybe we could attempt this, backporting
> security
> fixes from MariaDB 10.1 or forward-porting them from MariaDB 5.5 (still
> supported until April 2020). That way we don't force any 10.0 -> 10.1
> migration
> on our users (though MySQL 5.5 users will still
Hi Otto,
On Wed, Feb 27, 2019 at 04:32:24PM +0200, Otto Kekäläinen wrote:
> > Thinking about this some more, maybe we could attempt this, backporting
> > security
> > fixes from MariaDB 10.1 or forward-porting them from MariaDB 5.5 (still
> > supported until April 2020). That way we don't force
On 03/01/2019 11:20, Emilio Pozuelo Monfort wrote:
> On 03/01/2019 10:40, Otto Kekäläinen wrote:
>> Hello!
>>
>> to 3. tammik. 2019 klo 3.40 Robie Basak (robie.ba...@canonical.com)
>> kirjoitti:
>>>
>>> Hi Otto and the LTS team,
>>>
>>> On Mon, Dec 31, 2018 at 10:50:34AM +0200, Otto Kekäläinen
Hi
If we can avoid migration I think that is the safest approach. I just had a
failed upgrade (in current stable) and I'm guessing it can be a problem in
other cases too.
Migrating through .sql files works, but please note that this can be a very
disk and time consuming process. For small
On 2019-01-03 10:40, Otto Kekäläinen wrote:
You can always cross-migrate via logical database dumps as .sql files
instead of in-place binary files.
This is not guaranteed to work, and you need to take special care with
mysqldump and mysql options for such migration dumps.
For instance, if
On 03/01/2019 10:40, Otto Kekäläinen wrote:
> Hello!
>
> to 3. tammik. 2019 klo 3.40 Robie Basak (robie.ba...@canonical.com) kirjoitti:
>>
>> Hi Otto and the LTS team,
>>
>> On Mon, Dec 31, 2018 at 10:50:34AM +0200, Otto Kekäläinen wrote:
>>> I think that is *if* makes sense to engineer some
Hello!
to 3. tammik. 2019 klo 3.40 Robie Basak (robie.ba...@canonical.com) kirjoitti:
>
> Hi Otto and the LTS team,
>
> On Mon, Dec 31, 2018 at 10:50:34AM +0200, Otto Kekäläinen wrote:
> > I think that is *if* makes sense to engineer some automatic upgrade path in
> > an LTS release, then it
Hi Otto and the LTS team,
On Mon, Dec 31, 2018 at 10:50:34AM +0200, Otto Kekäläinen wrote:
> I think that is *if* makes sense to engineer some automatic upgrade path in
> an LTS release, then it would be to introduce MariaDB 10.1 into Jessie.
If this is explicitly opted in to by users then I
Hello Debian LTS team!
I think that is *if* makes sense to engineer some automatic upgrade path in
an LTS release, then it would be to introduce MariaDB 10.1 into Jessie.
Upgrading from MySQL 5.5 and MariaDB 10.0 to MariaDB 10.1 is pretty safe,
and the maintenance period of MariaDB 10.1 would
Hello!
pe 28. jouluk. 2018 klo 9.27 Jan Ingvoldstad
(jan-debian-lts-2...@oyet.no) kirjoitti:
>
> On 2018-12-27 18:51, Lars Tangvald wrote:
>
> > Upgrading to 5.6 would be less risky than MariaDB 10.1, but it's a
> > similar sort of risk.
>
> I don't know what the risk with switching to MariaDB
On 2018-12-27 18:51, Lars Tangvald wrote:
Upgrading to 5.6 would be less risky than MariaDB 10.1, but it's a
similar sort of risk.
I don't know what the risk with switching to MariaDB 10.1 would be, but
as a general principle, MariaDB lags behind (the already annoyingly
delayed) Oracle
Hi,
On 19.12.2018 17:01, Holger Levsen wrote:
Hi Emilio,
thanks for bringing up this issue on the LTS list.
On Mon, Dec 17, 2018 at 10:49:57AM +0100, Emilio Pozuelo Monfort wrote:
MySQL 5.5 should be EOL this month if nothing has changed, although I don't see
an announcement on [1] yet.
Hello!
ke 19. jouluk. 2018 klo 18.01 Holger Levsen (hol...@layer-acht.org) kirjoitti:
> > Also note that mariadb 10.0 is EOL in three months[2].
>
> I think this rules out mariadb 10.0 as a sensible upgrade path here.
> (Also, switching from mysql to mariadb in an LTS security upload???)
Do we
Hi Emilio,
thanks for bringing up this issue on the LTS list.
On Mon, Dec 17, 2018 at 10:49:57AM +0100, Emilio Pozuelo Monfort wrote:
> MySQL 5.5 should be EOL this month if nothing has changed, although I don't
> see
> an announcement on [1] yet. Maybe it will be published next month when the
On Mon, 17 Dec 2018 10:49:57 +0100
Emilio Pozuelo Monfort wrote:
> MySQL 5.5 should be EOL this month if nothing has changed, although I
> don't see an announcement on [1] yet. Maybe it will be published next
> month when the next CPU (critical patch update) is released. Norvald,
> do you know
Hi,
On 22/05/2018 07:10, Lars Tangvald wrote:
>
>
> On 05/21/2018 03:22 PM, Matus UHLAR - fantomas wrote:
Am 22.01.2018 um 13:42 schrieb Lars Tangvald:
> First off, thanks for handling the 5.5.59 update for Wheezy. I had the
> security announcement date mixed up so picked it up too
On 05/21/2018 03:22 PM, Matus UHLAR - fantomas wrote:
Am 22.01.2018 um 13:42 schrieb Lars Tangvald:
First off, thanks for handling the 5.5.59 update for Wheezy. I had the
security announcement date mixed up so picked it up too late, sorry.
MySQL 5.5 is expected to be EOL in December (it was
Am 22.01.2018 um 13:42 schrieb Lars Tangvald:
First off, thanks for handling the 5.5.59 update for Wheezy. I had the
security announcement date mixed up so picked it up too late, sorry.
MySQL 5.5 is expected to be EOL in December (it was first released
December 15, 2010, and we have 8 year
Hi,
On 01/23/2018 10:32 PM, Markus Koschany wrote:
Am 23.01.2018 um 11:41 schrieb Lars Tangvald:
Hi,
On 01/22/2018 04:35 PM, Markus Koschany wrote:
[...]
I also think it makes sense to take a smaller step and upgrade from 5.5
to 5.6. Are there any known issues with 5.6 or can you share any
On 01/24/2018 08:02 AM, Moritz Mühlenhoff wrote:
On Tue, Jan 23, 2018 at 11:41:57AM +0100, Lars Tangvald wrote:
I can't find much of anything that has changed from 5.5 to 5.6 in terms of
default behavior, except for NO_ENGINE_SUBSTITUTION being the default
sql_mode
On 2018-01-24 08:02, Moritz Mühlenhoff wrote:
That sounds far too disruptive for an LTS; better declare announce the server
part of mysql (where all the vulnerabilities apply) as unsupported in advance
and in December change the package to only build the libmysqlclient parts.
The client library
On Tue, Jan 23, 2018 at 11:41:57AM +0100, Lars Tangvald wrote:
> I can't find much of anything that has changed from 5.5 to 5.6 in terms of
> default behavior, except for NO_ENGINE_SUBSTITUTION being the default
> sql_mode
>
Am 23.01.2018 um 11:41 schrieb Lars Tangvald:
> Hi,
>
> On 01/22/2018 04:35 PM, Markus Koschany wrote:
[...]
>> I also think it makes sense to take a smaller step and upgrade from 5.5
>> to 5.6. Are there any known issues with 5.6 or can you share any
>> information about expected regressions
Hi,
On 01/22/2018 04:35 PM, Markus Koschany wrote:
Hi,
Am 22.01.2018 um 13:42 schrieb Lars Tangvald:
Hi,
First off, thanks for handling the 5.5.59 update for Wheezy. I had the
security announcement date mixed up so picked it up too late, sorry.
MySQL 5.5 is expected to be EOL in December
Hi,
Am 22.01.2018 um 13:42 schrieb Lars Tangvald:
> Hi,
>
> First off, thanks for handling the 5.5.59 update for Wheezy. I had the
> security announcement date mixed up so picked it up too late, sorry.
>
> MySQL 5.5 is expected to be EOL in December (it was first released
> December 15, 2010,
Hi,
First off, thanks for handling the 5.5.59 update for Wheezy. I had the
security announcement date mixed up so picked it up too late, sorry.
MySQL 5.5 is expected to be EOL in December (it was first released
December 15, 2010, and we have 8 year security support), while Jessie
LTS is
26 matches
Mail list logo
