Uploaded image for project: 'MariaDB ColumnStore'
  1. MariaDB ColumnStore
  2. MCOL-1712

Non consistent package name scheme for published mcsapi and data-adapter packages

    XMLWordPrintable

Details

    • Task
    • Status: Closed (View Workflow)
    • Minor
    • Resolution: Won't Do
    • 1.1.5, 1.1.6
    • Icebox
    • ?
    • None
    • Debian Ubuntu
    • 2018-17, 2018-18, 2018-19

    Description

      The published mcsapi packages are missing the release information as well as the "stretch", "xenial" and "jessie" parts in Debian 8, 9 and Ubuntu 16.
      But the published mcsapi packet names for Ubuntu Bionic contains the release information, and the mcsapi packet name for CentOS 7 contains the release information as well as the "centos7" part.

      The published maxscale cdc packet names are missing the release information, as well as the "stretch", "xenial" and "jessie" parts in Debian 8, Debian 9, and Ubuntu 16.
      But the published maxscale cdc packet names for Ubuntu Bionic contains the release information, and the mcsapi packet name for CentOS 7 contains the release information as well as the "centos7" part.

      The published maxscale avro packet names are missing the release information and "stretch", "xenial", "jessie" parts in Debian 8, Debian 9 and Ubuntu 16.
      But the published maxscale avro packet names for Ubuntu Bionic contains the release information, and the mcsapi packet name for CentOS 7 contains the release information as well as the "centos7" part.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              jens.rowekamp Jens Röwekamp (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 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.