Hi Michael!
Michael Biebl ,
20/09/2019 – 22:20:22 (+0200):
> Regarding my feedback, I guess the answer depends on what the goals of
> upstream are and Debian.
>
> Is the goal to keep the mysql aliasing or not?
>
> From what I gathered from the upstream bug report, upstream (at least
> one vocal one) was adamant that the mysql aliasing was not desired.
Yes and I believe that this could only be achieved in 10.5 but I may be
wrong, and I am trying to see with Sergei what is the better way for
moving forward (see my last comment here
https://jira.mariadb.org/browse/MDEV-15526?focusedCommentId=134361 and
here https://github.com/MariaDB/server/pull/1172)
> If that is the case, then I guess renaming /etc/init.d/mysql to
> /etc/init.d/mariadb and dropping the symlinks is the way to go.
Yes, I agree but starting 10.4.6, there is already another solution of
deploying mysql sysv init script in /usr/share/mysql instead of
/etc/init.d/mysql (see
https://github.com/mariadb/server/commit/a4cc6fb91f3855e0ed803a6e1762440cfcf8cb5c).
So for the moment, I would like to fix 2 things:
- new installation of version before 10.4.6 (and particularly 10.3 that
is the branch shipped in Buster);
- the upgrade situation (from any version before 10.4.6).
To address the upgrade situation, I don't see any better solution than
shipping static symlink in the package and to remove aliases from the
unit file. But there maybe another one?
> So my answer depends on what you are trying to achieve ultimately
> (downstream and/or upstream)
Ok, so let's wait and see if this can be done upstream, if not I will
try to have it for the next Debian release at least for 10.3 branch
first. I believe that in some very specific scenarios (replication or
SQL load balancing for instance) MDEV-15526 can have some serious
consequences.
Faustin
signature.asc
Description: PGP signature
