Your message dated Wed, 25 Dec 2024 13:39:12 +0000
with message-id <e1tqrbu-00bzqg...@fasolo.debian.org>
and subject line Bug#853008: fixed in mysql-8.0 8.0.40-2
has caused the Debian Bug report #853008,
regarding mysql-server-5.7: purge could delete mariadb-server files with
inadequate warning
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 ow...@bugs.debian.org
immediately.)
--
853008: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853008
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mysql-server-5.7
Version: 5.7.16-2
Severity: serious
Hello!
I'm really confused by the change in the postrm introduced in response
to LP: #1602945, and I simply do not understand the rationale of the
original bug report, and the comment there (and in the git commit log)
that "Remove the check on the server binary, since it shouldn't be
possible for another package to own that file anyway" is clearly
incorrect: during a postrm remove|purge run, if that file exists -
which it may well do, it will certainly belong to a different package,
such as mysql-server-5.8 or mariadb-server-10.1.
Regarding upgrading, I have upgraded from mysql-5.6 to mariadb-10.0
with no noticeable problems whatsoever. I have done a file comparison
looking for differences between /var/lib/mysql following this
mysql->mariadb conversion and a clean mariadb installation, and the
only ones I could see are:
mysql/ndb_binlog_index.*
mysql/slave_master_info.*
mysql/slave_relay_log_info.*
mysql/slave_worker_info.*
auto.cnf
If it is really the case the mariadb needs a different set of files
from mysql because of incompatibilities, then they should not share
the same /var/lib/mysql or it should be addressed in some other way:
mariadb could use /var/lib/mariadb instead, for instance, or the
mariadb installation could run some "clean up old /var/lib/mysql
directory from mysql instance" (which I think it already does).
So by removing the check on the existence of /usr/sbin/mysqld, you
leave sysadmins with the potential to inadvertantly wipe their entire
running mysql instance's database, for example if they purge an old
mysql-server-5.7 after installing mysql-server-5.8 at some point in
the future!
So as long as the various mysql/mariadb servers share the
/var/lib/mysql directory, the check for /usr/sbin/mysqld must be
reinstated: I cannot think of any situation in which rm -rf
/var/lib/mysql would be desired if /usr/sbin/mysqld is present, as
this means that there is some other package with responsibility for
/var/lib/mysql installed, and therefore this would fail the Debian
policy directive of not interferiyng with other packages' data. (And
that is why I have labelled this bug as severity "serious".) If a
sysadmin really wants to delete the directory in this situation, they
are welcome to do so manually.
The patch for this is simple: simply revert commit
554ecf472109f2b2e2fdfa0aaa0302cf2247ac1e
This would reopen the LP bug report, and I would ask the original
reporter there to explain the circumstances in which there are
problems, so that those can be addressed appropriately.
In addition, the current postrm_remove_databases debconf
question should be enhanced to explicitly mention mariadb. I would
also suggest being even more explicit: instead of "the data should be
kept", say "do NOT remove the databases, and say NO to this question."
Best wishes,
Julian
--- End Message ---
--- Begin Message ---
Source: mysql-8.0
Source-Version: 8.0.40-2
Done: Lena Voytek <lena.voy...@canonical.com>
We believe that the bug you reported is fixed in the latest version of
mysql-8.0, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 853...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Lena Voytek <lena.voy...@canonical.com> (supplier of updated mysql-8.0 package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Wed, 25 Dec 2024 08:07:22 -0500
Source: mysql-8.0
Built-For-Profiles: noudeb
Architecture: source
Version: 8.0.40-2
Distribution: unstable
Urgency: medium
Maintainer: Debian MySQL Maintainers <pkg-mysql-ma...@lists.alioth.debian.org>
Changed-By: Lena Voytek <lena.voy...@canonical.com>
Closes: 853008
Changes:
mysql-8.0 (8.0.40-2) unstable; urgency=medium
.
* Avoid removal of MariaDB database during install and purge
(Closes: #853008)
- d/mysql-server-8.0.preinst: Check for MariaDB version in existing
database and move data and notify user to avoid data loss.
- d/mysql-server-8.0.postrm: Check for MariaDB version before purging
database and skip data removal if it is found.
Checksums-Sha1:
566fa7102c2a3b39b93b83fa47c942eb6c31502b 3764 mysql-8.0_8.0.40-2.dsc
379d242a668ba613cc8be038ab8da6582db48b6a 146476
mysql-8.0_8.0.40-2.debian.tar.xz
36ebe594209f40c21db2853ade7d4fd9a5ebbd9f 8507
mysql-8.0_8.0.40-2_source.buildinfo
Checksums-Sha256:
2ccba9a1fd988b4c75b0b4f5ca8604d6f71b85d84e2aa35ed5eac3f7c7f86504 3764
mysql-8.0_8.0.40-2.dsc
9a4e92f2b41dc766c5e314b0559325f9e0ea3c969d16d1ba7b0902d9008a3793 146476
mysql-8.0_8.0.40-2.debian.tar.xz
97b36cacc2de3b31eb72bd12e25436156c98b2c4c5fb1e23d02962b80a2b4358 8507
mysql-8.0_8.0.40-2_source.buildinfo
Files:
6187ceb1b79d80b43464255cfcede28d 3764 database optional mysql-8.0_8.0.40-2.dsc
7d1e7e23ee132f1f4ef10ab501f7ad59 146476 database optional
mysql-8.0_8.0.40-2.debian.tar.xz
0732fef4e9867fa6b0bc41ef807e8b52 8507 database optional
mysql-8.0_8.0.40-2_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJOBAEBCgA4FiEEY+78PeFNUUbOfyS/NLitfZUp55MFAmdsBm8aHGxlbmEudm95
dGVrQGNhbm9uaWNhbC5jb20ACgkQNLitfZUp55PpGA/+MLoEQYV35Emg2jJCHsDz
1N5gpwaC74ehPdedMoG+B5rLnNxGQD2SzZUkbKd5+ukJCOK0dvgCHaNUarCZadCE
8hx0kSilZN2T7MjgfpcJW0clL2a/mz1Er8PUbHqrXUV1brUf6VIjy0dRRgmb9Ki/
rfol237mAcejhIB1oqxnfbBE+7BG7YFvj6u4L8ItENa+lgfvQGuK+/eSch6SdGYX
iYjFWeqYnVQEXTWKDll1C9pekYY3Wb82oGHOW7f2yAiVlSXbCVGGJ+T8J++KH5Px
uCJv99rjNUr+DnB/VPJAo5P6Vhjafr+eJGhOsj72mJE6IiFmDk2aum15TsKRsT5R
+uM6o2gvZdlv9SJ6QzePwYorJmlGJZy+ziv422a/9AHhLLrxqInA8qWXfu6VBY2a
KmIjofoOrBTp/7s3eLkEA/96rL48n3LZC/yiG6ZtAxkJGXae9Mv9aH80bidslI5u
uYFjLIooI4iEESlVbmwicrGJ0cqZKctbdE4FZjP47iSnO7FvX4NGrlp3tCCJDoA+
oOXMLLU28uu36NchFeAXyBsWLgYxD22m/w4/6jPPlmLBlZapu1YS+j6BuTP2uSXZ
WHz9lXq0hYnL5D9YMb6DhuyzTOWffkYLXzkoh2bBfQGfJWhTwvexxdaMfc8b83Gw
TItfPqGyn/iKrm6M06edAQg=
=NIbu
-----END PGP SIGNATURE-----
pgpy2dTf96DrH.pgp
Description: PGP signature
--- End Message ---
