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

[Ondřej Surý]

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.

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.

Cheers,
-- 
Ondřej Surý <ondrej at sury.org>
Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server
Knot Resolver (https://www.knot-resolver.cz/) – secure, privacy-aware,
fast DNS(SEC) resolver
Vše pro chleba (https://vseprochleba.cz) – Mouky ze mlýna a potřeby pro
pečení chleba všeho druhu

On Sat, Apr 29, 2017, at 15:44, Andreas Beckmann wrote:
> > 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")?
> 
> From my experience with piuparts:
> If there is no Depends: mysql-server in jessie (and no Depends:
> default-mysql-server in stretch), but the database is only pulled in via
> Recommends (or Suggests or even only manually), it is likely that
> mysql-server-5.5 gets removed during the dist-upgrade, without a
> replacement getting installed. mysql-server-5.5 *cannot* survive the
> upgrade to stretch due to Breaks/Conflicts somewhere (could have been
> libstdc++v5 or mariadb-client or ...) - even if *no* mariadb-server gets
> installed.
> 
> In piuparts mysql+postgres are the only services that are allowed to be
> started in a chroot - because that is often more useful than testing for
> behavior without a database running ...
> In piuparts I have a hardcoded list of packages that benefit from a
> database server (but only recommend it), and that server gets installed
> before that packages to be tested (s.t. it is running at test-package
> install time).
> piuparts usually runs a single pass apt-get dist-upgrade (no apt-get
> upgrade first), with the exception of database servers being upgraded
> first (s.t. the new database is running before the database users get
> upgraded). Otherwise database users that don't depend on a server
> usually get configured (and fail) while the database server has not been
> started again.
> For stretch I also maintain a hardcoded list of packages where I need to
> install default-mysql-server "manually" during the upgrade from jessie,
> since the decision was not to have an automatic migration from
> mysql-server to default-mysql-server if that was only manually installed
> by the admin.
> 
> Andreas
> 
> _______________________________________________
> pkg-mysql-maint mailing list
> pkg-mysql-maint at lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-mysql-maint