Bug#860970: marked as done (release-notes: MariaDB vs MySQL section 2.2.3 needs clarifying on how to perform the upgrade)
Your message dated Thu, 25 May 2017 09:29:40 +0200
with message-id <1495697380.3725871.988036128.498A9F01@webmail.messagingengine.com>
and subject line Re: [debian-mysql] FWD [Re: Bug#860970: release-notes: MariaDB vs MySQL section 2.2.3 needs clarifying on how to perform the upgrade]
has caused the Debian Bug report #860970,
regarding release-notes: MariaDB vs MySQL section 2.2.3 needs clarifying on how to perform the upgrade
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact email@example.com
Debian Bug Tracking System
Contact firstname.lastname@example.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <email@example.com>
- Subject: release-notes: MariaDB vs MySQL section 2.2.3 needs clarifying on how to perform the upgrade
- From: Paul Gevers <firstname.lastname@example.org>
- Date: Sat, 22 Apr 2017 22:45:09 +0200
- Message-id: <email@example.com>
-----BEGIN PGP SIGNED MESSAGE-----
I am very glad to see section 2.2.3 in the release-notes. However, I don't
think it is clear from the current text that there will not be any *-server
installed if no precausion is taken (at least, that is my experience and
understanding of the dependencies). mysql-server will be uninstalled during the
upgrade, and only when the default-mysql-server from debian-backports is
installed will the server be automatically replaced by the MariaDB server.
I suggest something like:
MariaDB is now the default MySQL variant in Debian, at version 10.1. The
Stretch release introduces a new mechanism for switching the default variant,
using metapackages created from the mysql-defaults source package. For example,
installing the metapackage default-mysql-server will install
mariadb-server-10.1. For upgrading from jessie, it is recommended to install
this metapackage from the jessie-backports archive so that users who have
mysql-server-5.5 or mysql-server-5.6 will have it removed and replaced
by the MariaDB equivalent. Similarly, installing default-mysql-client will
- -- System Information:
Debian Release: 9.0
APT prefers testing-debug
APT policy: (500, 'testing-debug'), (500, 'testing'), (200, 'experimental'), (200, 'testing'), (50, 'experimental'), (50, 'testing'), (1, 'experimental')
Kernel: Linux 4.9.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
-----BEGIN PGP SIGNATURE-----
-----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
- To: Paul Gevers <firstname.lastname@example.org>, email@example.com, firstname.lastname@example.org, Vincent McIntyre <email@example.com>
- Subject: Re: [debian-mysql] FWD [Re: Bug#860970: release-notes: MariaDB vs MySQL section 2.2.3 needs clarifying on how to perform the upgrade]
- From: Ondřej Surý <firstname.lastname@example.org>
- Date: Thu, 25 May 2017 09:29:40 +0200
- Message-id: <1495697380.3725871.988036128.498A9F01@webmail.messagingengine.com>
- In-reply-to: <email@example.com>
- References: <firstname.lastname@example.org> <email@example.com> <1493494724.3098967.960482120.34B2FBE1@webmail.messagingengine.com> <firstname.lastname@example.org> <email@example.com>
With introduction of src:mysql-transitional (providing dummy
mysql-server and mysql-client packages), the update to section 2.2.3 is
not needed anymore, as the mysql-server 5.5.9999+default will pull
default-mysql-server forcing the upgrade even in the case when nothing
depends on mysql-server.
Ondřej Surý <firstname.lastname@example.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 23:44, Ondřej Surý wrote:
> 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 <email@example.com> 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
> > firstname.lastname@example.org
> > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-mysql-maint
> pkg-mysql-maint mailing list
--- End Message ---