On 02/21/2017 01:59 PM, Julian Gilbey wrote:
On Tue, Feb 21, 2017 at 01:27:44PM +0100, Lars Tangvald wrote:
I've looked at it some more, and I'm hesitant about including such a big
patch for a pretty rare scenario, which in the worst case does ask the
following:
The /var/lib/mysql directory which contains the MySQL databases is about
to be removed.
.
This will also erase all data in /var/lib/mysql-files as well as
/var/lib/mysql-keyring.
.
If you're removing the MySQL package in order to later install a more
recent version or if a different mysql-server package is already
using it, the data should be kept.
My suggestion is that for now, we revert the patch that enabled the
purge-remove (meaning postrm will never delete anything or ask to do so) and
instead work on separating the data for the different packages so that
MariaDB and MySQL data isn't in the same location.
Hi Lars,
Does that mean that the whole remove section just gets removed from
the postrm, or that you put back the test for /usr/sbin/mysqld existing?
Best wishes,
Julian
Only reverting the commit would put it back, which I guess would be best
since I think it can trigger if you first do apt-get remove and then
apt-get purge (without installing a different variant between).
--
Lars
