Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-17367

mysql_install_db requires my_print_defaults, but my_print_defaults is in mariadb-server-10.1

Details

    Description

      mysql_install_db is installed by mariadb-server-core and requires my_print_defaults that is provided by package mariadb-server.

      Step to reproduce (on 10.1 and 10.3):

      $ sudo apt install mariadb-server-core-10.1
      $ /usr/bin/mysql_install_db
       
      FATAL ERROR: Could not find /usr/bin/my_print_defaults
      ...
      

      This was signaled by Alex Hvostov:
      https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898367

      Attachments

        Issue Links

          Activity

            Does it create any practical problem? mysql_install_db won't work anyway if the server is not installed.

            elenst Elena Stepanova added a comment - Does it create any practical problem? mysql_install_db won't work anyway if the server is not installed.

            No, no other problem that script not found.
            Is it possible to use mysql_install_db on a remote DB, this is the only reason where this could be considered as an issue for me...

            faust Faustin Lammler added a comment - No, no other problem that script not found. Is it possible to use mysql_install_db on a remote DB, this is the only reason where this could be considered as an issue for me...

            mysql_install_db starts the server process in order to bootstrap the database, so it has to be local.
            And even if it were possible, my_print_defaults still would need to be on the machine where the server runs (and not the client), since it reads server configuration files.

            elenst Elena Stepanova added a comment - mysql_install_db starts the server process in order to bootstrap the database, so it has to be local. And even if it were possible, my_print_defaults still would need to be on the machine where the server runs (and not the client), since it reads server configuration files.
            faust Faustin Lammler added a comment - - edited

            Thank you elenst for this quick answer!

            So this is clearly not an issue. But I do not know if this is an acceptable situation regarding the Debian packaging guidelines.
            I have to check this point (anybody aware on that please let me know).

            faust Faustin Lammler added a comment - - edited Thank you elenst for this quick answer! So this is clearly not an issue. But I do not know if this is an acceptable situation regarding the Debian packaging guidelines. I have to check this point (anybody aware on that please let me know).

            cvicentiu, maybe you can help with that (or know who can)?

            elenst Elena Stepanova added a comment - cvicentiu , maybe you can help with that (or know who can)?

            elenst what do you think about Olaf comment?
            https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898367#15

            I have just asked Viventiu on zulip also.

            faust Faustin Lammler added a comment - elenst what do you think about Olaf comment? https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898367#15 I have just asked Viventiu on zulip also.
            elenst Elena Stepanova added a comment - - edited

            I don't have any strong preferences regarding Debian packaging, to a big extent it seems arbitrary to me. Maybe serg has an opinion. In any case, I hope cvicentiu will be able to coordinate it to everyone's satisfaction.

            elenst Elena Stepanova added a comment - - edited I don't have any strong preferences regarding Debian packaging, to a big extent it seems arbitrary to me. Maybe serg has an opinion. In any case, I hope cvicentiu will be able to coordinate it to everyone's satisfaction.

            it's not about remote server or anything. It's the simple thing that if a package X uses something from the package Y, it needs to depend on the package Y, and this is not the case here.

            serg Sergei Golubchik added a comment - it's not about remote server or anything. It's the simple thing that if a package X uses something from the package Y, it needs to depend on the package Y, and this is not the case here.

            That seems clear an logic to me.
            Let's wait for cvicentiu decision.

            faust Faustin Lammler added a comment - That seems clear an logic to me. Let's wait for cvicentiu decision.

            Hi,
            commit on debian repo from otto resolves this issue:
            https://salsa.debian.org/mariadb-team/mariadb-10.1/commit/3689350ad30916aa68fe2c1b35c290fb5095bc9b

            It should be updated on upstream too and this is maybe already in otto's wip list?

            faust Faustin Lammler added a comment - Hi, commit on debian repo from otto resolves this issue: https://salsa.debian.org/mariadb-team/mariadb-10.1/commit/3689350ad30916aa68fe2c1b35c290fb5095bc9b It should be updated on upstream too and this is maybe already in otto's wip list?
            otto Otto Kekäläinen added a comment - PR filed at https://github.com/MariaDB/server/pull/1451

            PR https://github.com/MariaDB/server/pull/1451 was merged, thus this issue is closed for 10.5.

            otto Otto Kekäläinen added a comment - PR https://github.com/MariaDB/server/pull/1451 was merged, thus this issue is closed for 10.5.

            People

              otto Otto Kekäläinen
              faust Faustin Lammler
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.