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

Can't build Debian packages from the generic .tar.gz sources file, its debian/ directory seems incomplete

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Trivial
    • Resolution: Not a Bug
    • Affects Version/s: 5.5.28a
    • Fix Version/s: 5.5.30
    • Component/s: None
    • Labels:
      None
    • Environment:
      Debian Squeeze amd64

      Description

      I wanted to have the sources and especially the debian/ directory from the 5.5.25 release so i could try to create Debian packages for TokuDB (latest version is based on MariaDB 5.5.25 which is not the latest release as of now) but there is only the latest release source package available on the Debian/Ubuntu repositories, so i tried to use the "mariadb-5.5.25.tar.gz" non distro-specific sources that includes the "debian/" directory normally used for Debian/Ubuntu packages creation.

      Unfortunately, if you try to do a dpkg-buildpackage from these sources, you will hit errors telling you that mandatory files are missing from the "debian/" directory :

      [...]
      dpkg-buildpackage: host architecture amd64
      dpkg-buildpackage: warning: debian/rules is not executable: fixing that.
      dpkg-source --before-build mariadb-5.5.28a
      dpkg-source: error: cannot read mariadb-5.5.28a/debian/control: No such file or directory
      dpkg-buildpackage: error: dpkg-source --before-build mariadb-5.5.28a gave error exit status 2

      The debian/ directory size is bit smaller on the tarball version than the repository one and some files are missing :

      $ du -s mariadb-5.5-5.5.28-mariadb/debian/ mariadb-5.5.28a/debian/
      1392 mariadb-5.5.28a/debian/
      1448 mariadb-5.5-5.5.28-mariadb/debian/

      Is this an expected behavior (in that case, where could i retreive a working debian/ directory from a previous release) or a bug?

      ps: same problem happens on 5.5.28a and 5.5.25.

        Gliffy Diagrams

          Attachments

            Activity

            Hide
            knielsen Kristian Nielsen added a comment -

            The reason for the build failures is that some files need to be symlinked in
            place (and different files depending on whether building for Ubuntu or
            Debian).

            The script debian/autobake-deb.sh handles this. This script is what is run to
            build the .deb packages from the source tarball.

            Alternatively, I believe `apt-get source` can be used to grab a source package
            in .deb format, which should have everything in place for standard .deb build
            tools.

            Show
            knielsen Kristian Nielsen added a comment - The reason for the build failures is that some files need to be symlinked in place (and different files depending on whether building for Ubuntu or Debian). The script debian/autobake-deb.sh handles this. This script is what is run to build the .deb packages from the source tarball. Alternatively, I believe `apt-get source` can be used to grab a source package in .deb format, which should have everything in place for standard .deb build tools.

              People

              • Assignee:
                knielsen Kristian Nielsen
                Reporter:
                jb-boin Jean Weisbuch
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 15 minutes
                  15m