[debian-mysql] [MBF] mysql meta-packages

[Robie Basak]

On Sat, Dec 17, 2016 at 10:46:58PM +0100, Andreas Beckmann wrote:
> Therefore I would suggest the following:
> 
> Let's build a transitional mysql-server package from src:mysql-defaults
> and have that depend on default-mysql-server. Version would be something
> along 5.7.16+1.0.2 to take over the package from src:mysql-5.7
> Temporarily stop building mysql-server from src:mysql-5.7 until the
> freeze is over. After the freeze and after mysql-5.7 had a new upstream
> release, build the package again from src:mysql-5.7.

We're still maintaining mysql-5.7 in sid, so I'm not particularly keen
on this.

What happens if mysql-5.7 has a new upstream release before the freeze
is over? I recall enquiries in the past asking for upstream security
update releases soon after they appear. Would we be blocked from being
able to upload these?

We also have the same issue as in the other thread that mariadb-server
doesn't behave exactly the same as mysql-server. Additionally,
automatically transitioning users results in DB changes that cannot be
reversed (ie. the user cannot switch back to MySQL again without manual
intervention and ideally backups).

So I think my two objections are:

1) We have not decided to automatically switch users' data (effectively)
irreversably from MySQL to MariaDB on upgrade. This should have been
discussed at the time of making the decision to drop MySQL, but since
the release team treated that as a fait accompli by filing bug 837615,
that discussion never happened. Note that I'm saying that we have not
decided to, not that we have decided not to. We just haven't had a
discussion or made any decision.

2) We're still maintaining MySQL packaging; it doesn't seem reasonable
to halt progress or impede that because of the release team's desires
around stretch. Perhaps Debian's policies do allow this; in that case
I'd be happy to be corrected by being pointed to documented policies in
this area.

> Should we do the same for mysql-client? Any other package?

server, server-core, client and client-core? Perhaps some can be skipped
if nothing is depending on them, but those are the four that should be
checked I think.

> If you are interested, I could implement this.

My objections are as above. If you do implement this, please also deal
with any subsequent problems in relation to this change in both stretch
and sid.

Robie
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-mysql-maint/attachments/20161218/ed37719b/attachment.sig>