Bug#1029136: MariaDB configuration files not properly migrated on switch to unversioned packages

2023-02-05 Thread Otto Kekäläinen
> > This is now solved on > > https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests/31 > > Mangling the maintainers scripts of another package is a delicate issue > as it's often fragile and can cause hard to debug failures in corner cases. > > Personally, I would have turned the

Bug#1029136: MariaDB configuration files not properly migrated on switch to unversioned packages

2023-02-05 Thread Michael Biebl
Hi Otto Am 05.02.23 um 17:55 schrieb Otto Kekäläinen: This is now solved on https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests/31 Mangling the maintainers scripts of another package is a delicate issue as it's often fragile and can cause hard to debug failures in corner

Bug#1029136: MariaDB configuration files not properly migrated on switch to unversioned packages

2023-02-05 Thread Otto Kekäläinen
This is now solved on https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests/31

Bug#1029136: MariaDB configuration files not properly migrated on switch to unversioned packages

2023-01-30 Thread Michael Biebl
Am 30.01.23 um 07:59 schrieb Otto Kekäläinen: The only problem there is that on purge deb-systemd-helper and update-rc.d will disable the service, but that is not based on package ownership. The maintainer scripts will act on files which effectively no longer belong to this package. That's

Bug#1029136: MariaDB configuration files not properly migrated on switch to unversioned packages

2023-01-29 Thread Otto Kekäläinen
Hi! Here is the situation after 'apt full-upgrade -y': $ dpkg -l | grep -iE 'maria|mysql|galera' || true # List installed ii default-mysql-client 1.1.0 all MySQL database client binaries (metapackage) ii default-mysql-client-core 1.1.0 all

Bug#1029136: MariaDB configuration files not properly migrated on switch to unversioned packages

2023-01-29 Thread Michael Biebl
Am 29.01.2023 um 04:12 schrieb Otto Kekäläinen: Hi! I managed now to reproduce this. The purge step is not relevant, but simply the upgrade itself. ... -> upgrade successful, but service stopped working - the service file has no executable bit anymore. That's only half of the bug report.

Bug#1029136: MariaDB configuration files not properly migrated on switch to unversioned packages

2023-01-28 Thread Otto Kekäläinen
Hi! I managed now to reproduce this. The purge step is not relevant, but simply the upgrade itself. In clean Docker container with Debian unstable: $ apt install -y mariadb-server-10.6 -> install successful $ apt full-upgrade -y -> does nothing $ service mariadb restart Stopping MariaDB

Bug#1029136: MariaDB configuration files not properly migrated on switch to unversioned packages

2023-01-22 Thread Michael Biebl
Am 21.01.23 um 21:28 schrieb Otto Kekäläinen: Hi! I have been frantically trying to reproduce the issue you reported. It's trivial to reproduce: Have the versioned mariadb packages installed (say from unstable), then make an apt full-upgrade, which will install the new unversioned ones and

Bug#1029136: MariaDB configuration files not properly migrated on switch to unversioned packages

2023-01-21 Thread Otto Kekäläinen
Hi! I have been frantically trying to reproduce the issue you reported. Would you be able to describe more in detail what was the situation before and after you upgraded and what commands exactly did you do to execute the upgrade (apt upgrade, apt full-upgrade, apt-get, aptitude)? We might very

Bug#1029136: MariaDB configuration files not properly migrated on switch to unversioned packages

2023-01-20 Thread Otto Kekäläinen
Hi! Thanks for reporting the issue. I saw this earlier and fixed it via https://salsa.debian.org/mariadb-team/mariadb-server/-/commit/dd3a058ebec877da50aadc9f8909d61ac634430a - but cleary the fix does not fully work as you ran into this again. I will dive deeper. - Otto