Your message dated Sat, 22 Aug 2020 12:41:31 +0300 with message-id <CAHj_TLDJm7i_DGDc=s=bc9auehv0me23wrbup+4c7pe72n0...@mail.gmail.com> and subject line Re: [debian-mysql] Bug#851195: Bug#851195: Bug#851195: Bug#851195: mariadb-server-10.1: Time Zone system tables are empty has caused the Debian Bug report #851195, regarding mariadb-server-10.1: Time Zone system tables are empty 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.) -- 851195: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851195 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: mariadb-server-10.1 Severity: wishlist Tags: patch Dear Maintainer, * What led up to the situation? $ sudo apt-get install mariadb-server-10.1 * What exactly did you do (or not do) that was effective (or ineffective)? mysql> SELECT COUNT(*) FROM mysql.time_zone; * What was the outcome of this action? 0 * What outcome did you expect instead? 1820 or so This was unexpected because of #388491 - mysql-server-5.0: setup time_zone* tables upon installation? https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=388491 Apparently this change was lost somewhere between MySQL 5.0 and 5.1. I couldn't determine if this was accidental or intentional. Anyway, I propose the attached patch to the postinst script. Thank you! Dan--- mariadb-server-10.1.postinst.orig 2016-12-20 14:58:40.000000000 -0600 +++ mariadb-server-10.1.postinst 2017-01-12 00:00:00.000000000 -0600 @@ -157,6 +157,9 @@ # NOTE: $MYSQL_BOOTSTRAP requires one SQL statement per line, semicolon at the end. echo "$password_column_fix_query" | $MYSQL_BOOTSTRAP 2>&1 | $ERR_LOGGER + # Update timezone tables + mysql_tzinfo_to_sql /usr/share/zoneinfo 2>/dev/null | $MYSQL_BOOTSTRAP 2>&1 | $ERR_LOGGER + ;; abort-upgrade|abort-remove|abort-configure)--- mariadb-server-10.1.postinst.orig 2016-12-20 14:58:40.000000000 -0600 +++ mariadb-server-10.1.postinst 2017-01-12 00:00:00.000000000 -0600 @@ -157,6 +157,9 @@ # NOTE: $MYSQL_BOOTSTRAP requires one SQL statement per line, semicolon at the end. echo "$password_column_fix_query" | $MYSQL_BOOTSTRAP 2>&1 | $ERR_LOGGER + # Update timezone tables + mysql_tzinfo_to_sql /usr/share/zoneinfo 2>/dev/null | $MYSQL_BOOTSTRAP 2>&1 | $ERR_LOGGER + ;; abort-upgrade|abort-remove|abort-configure)
--- End Message ---
--- Begin Message ---> Based on discussions on #mariadb it seems that this table is maybe on > purpose empty, and it is up to the database admin to populate and keep > it updated. Anyway, the fix should be done upstream and then > identically applied here in Debian. If you want to invest more time in > this, please file and issue at jira.mariadb.org and mark this Debian > issue with "forwarded https...." Closing issue because of this. Please champion this upstream if you think all MariaDB installations should come with pre-polulated timezone data. Thanks!
--- End Message ---
