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

Fix issue with missing dependency socat when installing MariaDB-galera-server on RedhatEL/OracleEL/(Others?) RPM based

Details

    Description

      Hi,

      One who is trying to install MDBGC using our Repository doesn't install it because it fails, due to socat dependency, and because socat is not provided in the version I tested (Oracle Enterprise Linux 6.6)

      If I want to use MDBGC with this OS, I can't, unless I download manually the package

      The socat application is not necessary to operate MariaDB Galera Cluster. It is necessary only if you use the optionnal xtrabackup-v2 transfer method
      Socat is a dependecy of the percona-xtrabackup package, that one still needs to install manually.

      Solutions I see are:

      • we put socat in the mariadb repo.
      • we install xtrabackup as dependency. At least we fail for something.
      • we remove socat dependency.

      Thanks in advance,
      Joffrey

      Attachments

        Issue Links

          Activity

            Transition Time In Source Status Execution Times
            Nirbhay Choubey (Inactive) made transition -
            Open In Progress
            9d 10h 14m 1
            Nirbhay Choubey (Inactive) made transition -
            In Progress In Review
            17h 5m 1
            Sergei Golubchik made transition -
            In Review Stalled
            18h 57m 1
            Nirbhay Choubey (Inactive) made transition -
            Stalled Closed
            1h 20m 1

            People

              nirbhay_c Nirbhay Choubey (Inactive)
              joffrey Joffrey MICHAIE (Inactive)
              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.