Bug#860970: [debian-mysql] FWD [Re: Bug#860970: release-notes: MariaDB vs MySQL section 2.2.3 needs clarifying on how to perform the upgrade]

2017-04-29 Thread Ondřej Surý 
You don't have to run apt-get upgrade first. Just running apt install 
default-mysql-server should do the job.



On 29 April 2017 22:30:40 Paul Gevers  wrote:


Hi,

As a starter, I have been mixing 'apt-get update' and 'apt-get upgrade'
in my previous e-mails. Of course one always runs 'apt-get update'
before anything, I always meant 'apt(-get) upgrade' where 'update' is
mentioned. The release-notes propose to upgrade in two steps, first with
apt-get upgrade and then apt-get dist-upgrade. @Otto, did you also mean
the two step when you talked about "The upgrade has been
designed to work correctly by simply running 'apt-get update' and
'apt-get dist-upgrade'" or did you really mean upgrading in one step?

On 29-04-17 21:38, Ondřej Surý wrote:

Andreas,

I believe that your observation is in fact correct and the `apt-get
dist-upgrade` path will not upgrade mysql-5.5 to mariadb-10.1 if no
other package depends on default-mysql-server.

I had this conversation with Robbie when default-mysql-server was
introduced, and I argued that it would be much simpler to reuse the
original mysql-server name, but I wasn't able to convince him that
'mysql-server' should install mariadb-server-10.1, and there's a grain
of truth that people might expect to have Oracle's MySQL server
installed when they install 'mysql-server' package, so I stopped
pursuing the matter.

I don't think there's a better way how to approach the issue than in the
release note so deep in the freeze.


Ack.


What we could do (with the blessing of the release team) - is to
introduce the default-mysql-server into the jessie where it would just
simply mimic the existing setup, e.g. default-mysql-server would depend
on mysql-server and default-mysql-client would depend on mysql-client.
People could be then recommended to install default-mysql-server and
default-mysql-client prior to jessie->stretch upgrade, and in turn
having a smooth upgrade experience because mariadb-server-10.1 would
then installed during apt-get dist-upgrade step.


Sounds like a plan. But still, would my proposal for the text in the
release-notes not achieving nearly this without changes required in
jessie? My proposal being: run apt-get upgrade, apt-get install
default-mysql-server, apt-get dist-upgrade. I must admit I haven't
tested this and there may be issues I don't see.

Paul




--
___
pkg-mysql-maint mailing list
pkg-mysql-ma...@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-mysql-maint

Bug#860970: [debian-mysql] FWD [Re: Bug#860970: release-notes: MariaDB vs MySQL section 2.2.3 needs clarifying on how to perform the upgrade]

2017-04-29 Thread Paul Gevers 
Hi,

As a starter, I have been mixing 'apt-get update' and 'apt-get upgrade'
in my previous e-mails. Of course one always runs 'apt-get update'
before anything, I always meant 'apt(-get) upgrade' where 'update' is
mentioned. The release-notes propose to upgrade in two steps, first with
apt-get upgrade and then apt-get dist-upgrade. @Otto, did you also mean
the two step when you talked about "The upgrade has been
designed to work correctly by simply running 'apt-get update' and
'apt-get dist-upgrade'" or did you really mean upgrading in one step?

On 29-04-17 21:38, Ondřej Surý wrote:
> Andreas,
> 
> I believe that your observation is in fact correct and the `apt-get
> dist-upgrade` path will not upgrade mysql-5.5 to mariadb-10.1 if no
> other package depends on default-mysql-server.
> 
> I had this conversation with Robbie when default-mysql-server was
> introduced, and I argued that it would be much simpler to reuse the
> original mysql-server name, but I wasn't able to convince him that
> 'mysql-server' should install mariadb-server-10.1, and there's a grain
> of truth that people might expect to have Oracle's MySQL server
> installed when they install 'mysql-server' package, so I stopped
> pursuing the matter.
> 
> I don't think there's a better way how to approach the issue than in the
> release note so deep in the freeze.

Ack.

> What we could do (with the blessing of the release team) - is to
> introduce the default-mysql-server into the jessie where it would just
> simply mimic the existing setup, e.g. default-mysql-server would depend
> on mysql-server and default-mysql-client would depend on mysql-client.
> People could be then recommended to install default-mysql-server and
> default-mysql-client prior to jessie->stretch upgrade, and in turn
> having a smooth upgrade experience because mariadb-server-10.1 would
> then installed during apt-get dist-upgrade step.

Sounds like a plan. But still, would my proposal for the text in the
release-notes not achieving nearly this without changes required in
jessie? My proposal being: run apt-get upgrade, apt-get install
default-mysql-server, apt-get dist-upgrade. I must admit I haven't
tested this and there may be issues I don't see.

Paul



signature.asc
Description: OpenPGP digital signature

Bug#860970: [debian-mysql] FWD [Re: Bug#860970: release-notes: MariaDB vs MySQL section 2.2.3 needs clarifying on how to perform the upgrade]

2017-04-28 Thread Paul Gevers 
Hi all,

On 28-04-17 21:35, Otto Kekäläinen wrote:
> Please don't update the release notes like this. The upgrade has been
> designed to work correctly by simply running 'apt-get update' and
> 'apt-get dist-upgrade' until these and all other packages on the
> system have been updated. This has been tested countless times.
> Unfortunately Paul had a different experience on his NAS box when
> upgrading it, but that case is not the usual case and should not be
> the motivation to make new general recommendations.

I did *not* run 'apt-get update'/'apt-get dist-upgrade', but I ran 'apt
dist-upgrade' directly. I must admit that I remembered the meaning of
section 4.4.4 wrong. To avoid removing packages, it is indeed
recommended to do the two step.

Otto, are you now saying that without any action, mysql-server-5.x will
be upgraded to mariadb-server-10.1? If that is true, could that be made
more explicit in the text? If that isn't true, can it be made more
explicit when the system administrator is supposed to install
default-mysql-server during upgrades (that is what I tried to accomplish
in my "improvement")?

Maybe just mention that without update before dist-upgrade things go
wrong. That would already make my experience worth while.

Paul



signature.asc
Description: OpenPGP digital signature