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

Potential issue: sst_dump may already exist in Debian at installation time

Details

    • Bug
    • Status: Closed (View Workflow)
    • Trivial
    • Resolution: Fixed
    • 10.3(EOL)
    • 10.5.2
    • Platform Debian
    • None

    Description

      In commit a421f0b6b8feb41a42fc4cedfcd549d8e681e47b sst_dump was added to the mariadb-plugin-rocksdb package.

      This binary is also coming to Debian via the rocksdb-tools package. It is however currently now only in Debian experimental: https://packages.debian.org/experimental/rocksdb-tools

      We might drop it from our package or make our package conflict with rocksdb-tools.

      Attachments

        Issue Links

          blocks

          Task - A task that needs to be done. MDEV-6284 Merge downstream Debian/Ubuntu packaging into upstream MariaDB

          • Major - Major loss of function.
          • Closed

          Activity

            Ascending order - Click to sort in descending order
            View 5 older comments
            psergei Sergei Petrunia added a comment -

            .. so I think both solutions (removing sst_dump from packaging and renaming it to mysql_sst_dump, like it was done with ldb->mysql_ldb) are acceptable.

            psergei Sergei Petrunia added a comment - .. so I think both solutions (removing sst_dump from packaging and renaming it to mysql_sst_dump, like it was done with ldb->mysql_ldb) are acceptable.
            psergei Sergei Petrunia added a comment -

            otto, do I understand correctly that your patch removes sst_dump from MyRocks' package? (I think, this is ok). Will we need to merge this patch the MariaDB upstream repository? (or, what else there is to do for this MDEV?)

            psergei Sergei Petrunia added a comment - otto , do I understand correctly that your patch removes sst_dump from MyRocks' package? (I think, this is ok). Will we need to merge this patch the MariaDB upstream repository? (or, what else there is to do for this MDEV?)
            otto Otto Kekäläinen added a comment -

            Thanks for your analysis. Let's wait a bit for the change in Debian to become "battle-tested" and then upstream the same change.

            otto Otto Kekäläinen added a comment - Thanks for your analysis. Let's wait a bit for the change in Debian to become "battle-tested" and then upstream the same change.
            otto Otto Kekäläinen added a comment -

            PR filed at https://github.com/MariaDB/server/pull/1451

            otto Otto Kekäläinen added a comment - PR filed at https://github.com/MariaDB/server/pull/1451
            otto Otto Kekäläinen added a comment -

            PR was merged, but Jira issue did not auto-update?

            Anyway, this has been fixed since https://github.com/MariaDB/server/commit/f2832a010a4ab0ba1cd47cc378338731bf659328 landed.

            otto Otto Kekäläinen added a comment - PR was merged, but Jira issue did not auto-update? Anyway, this has been fixed since https://github.com/MariaDB/server/commit/f2832a010a4ab0ba1cd47cc378338731bf659328 landed.

            People

              otto Otto Kekäläinen
              otto Otto Kekäläinen
              Votes:
              0 Vote for this issue
              Watchers:
              5 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.