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

Invalid checksums for RPMs on archive.mariadb.org

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Critical
    • Resolution: Done
    • None
    • N/A
    • Packaging
    • None
    • Not for Release Notes

    Description

      Description:

      Checksums for several RPMs kept on archive.mariadb.org are invalid, and prevent installation with dnf. I have not checked extensively, but this appeared on regular testing of upgrades via GitLab CI, a mirror of which can be seen here: https://salsa.debian.org/robinnewhouse/mariadb-server-mirror/-/pipelines/647262.

      (upgrade test script: https://github.com/MariaDB/server/blob/11.5/tests/upgrade_from/test_upgrade.sh)

      The error for at least three versions shows

      [MIRROR] MariaDB-common-10.3.27-1.fc31.x86_64.rpm: Downloading successful, but checksum doesn't match. Calculated: d48a0f112d180059da25a2b09eca6a726d2f75c65cf193b98c726259549b0dc4(sha256)  Expected: 431307eb1d39979ce30667d1918b89126549ec3f0b00bd5fabafaf3583a1f75f(sha256) 
      ...
      [FAILED] MariaDB-common-10.3.27-1.fc31.x86_64.rpm: No more mirrors to try - All mirrors were already tried without success
      

      I have not exhaustively tested all distributions and architectures, so there may be more than are listed below.

      How to reproduce:

      Start a docker image using

      docker run --rm -it fedora:latest bash
      

      In the docker image

      # Instructions in https://mariadb.com/kb/en/yum/
      version=10.5
      distro_name=fedora
      distro_version=35
      arch=x86_64
      rpm_repository=https://archive.mariadb.org/mariadb-$version/yum/$distro_name/$distro_version/$arch/
      echo "rpm_repository=$rpm_repository"
      cat <<EOF >/etc/yum.repos.d/MariaDB.repo
      [mariadb]
      name = MariaDB
      baseurl = $rpm_repository
      gpgkey = https://archive.mariadb.org/PublicKey
      gpgcheck = 1
      EOF
      # Install missing dependancies depending on distribution version
      [[ $distro_version -le 32 ]] && dnf install -y https://download-ib01.fedoraproject.org/pub/epel/8/Everything/x86_64/Packages/b/boost169-program-options-1.69.0-5.el8.x86_64.rpm
      [[ $distro_version == 33 ]] && dnf install -y http://springdale.princeton.edu/data/springdale/7/x86_64/os/Computational/boost173-program-options-1.73.0-7.sdl7.x86_64.rpm
      [[ $distro_version == 34 ]] && dnf install -y https://repo.almalinux.org/almalinux/9/AppStream/x86_64/os/Packages/boost-program-options-1.75.0-8.el9.x86_64.rpm https://vault.centos.org/centos/8/AppStream/x86_64/os/Packages/liburing-1.0.7-3.el8.x86_64.rpm
      [[ $distro_version == 35 ]] && dnf install -y https://archives.fedoraproject.org/pub/archive/fedora/linux/updates/36/Everything/x86_64/Packages/b/boost-program-options-1.76.0-12.fc36.x86_64.rpm
      dnf install -y MariaDB-server
      

      I have reproduced this with

      10.5 / fedora 35
      10.4 / fedora 33
      10.3 / fedora 31

      This can also be seen by calculating the checksum

      > curl -LO https://archive.mariadb.org/mariadb-10.3/yum/fedora/31/x86_64/rpms/MariaDB-common-10.3.27-1.fc31.x86_64.rpm
      > sha256sum MariaDB-common-10.3.27-1.fc31.x86_64.rpm
      d48a0f112d180059da25a2b09eca6a726d2f75c65cf193b98c726259549b0dc4  MariaDB-common-10.3.27-1.fc31.x86_64.rpm
      

      Compared to
      https://archive.mariadb.org/mariadb-10.3/yum/fedora/31/x86_64/sha256sums.txt

      431307eb1d39979ce30667d1918b89126549ec3f0b00bd5fabafaf3583a1f75f  ./rpms/MariaDB-common-10.3.27-1.fc31.x86_64.rpm
      

      Attachments

        Activity

          People

            dbart Daniel Bartholomew
            robinnew Robin Newhouse
            Votes:
            0 Vote for this issue
            Watchers:
            7 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.