Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Duplicate
    • 5.5.30
    • None
    • None
    • None
    • Debian 7.0 x64

    Description

      root@minisql:~# apt-get install mariadb-server mariadb-server-5.5 mariadb-server-core-5.5 mariadb-client-5.5 mariadb-client libmariadbclient18 mariadb-client-core-5.5 libmysqlclient18

      Reading package lists... Done
      Building dependency tree
      Reading state information... Done
      libmysqlclient18 is already the newest version.
      Some packages could not be installed. This may mean that you have
      requested an impossible situation or if you are using the unstable
      distribution that some required packages have not yet been created
      or been moved out of Incoming.
      The following information may help to resolve the situation:

      The following packages have unmet dependencies:
      libmariadbclient18 : Depends: libmysqlclient18 (= 5.5.30-mariadb1~wheezy) but 5.5.30+dfsg-1.1 is to be installed
      E: Unable to correct problems, you have held broken packages.

      Attachments

        Issue Links

          Activity

            It's already fixed in the tree, 5.5.31 shouldn't have this problem

            serg Sergei Golubchik added a comment - It's already fixed in the tree, 5.5.31 shouldn't have this problem
            elenst Elena Stepanova added a comment - For now, you can use any of the workarounds described in the KB: https://kb.askmonty.org/en/installing-mariadb-deb-files/#version-mismatch-between-mariadb-and-ubuntudebian-repositories

            People

              Unassigned Unassigned
              oz42 Olaf Zaplinski
              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.