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

Bintar package cannot be used on latest Ubuntu 16.04 LTS: libsystemd-daemon.so.0: cannot open shared object file

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 10.1(EOL), 10.2(EOL)
    • N/A
    • Packaging
    • None

    Description

      I am trying bintar package on the latest Ubuntu 16.04.1 LTS Xenial.

      I get an error like this:

      ~/try-packages-1/mariadb-10.2.5-linux-x86_64$ ./bin/mysqld --defaults-file=~/my1.cnf 
      ./bin/mysqld: error while loading shared libraries: libsystemd-daemon.so.0: cannot open shared object file: No such file or directory

      Xenial has no package for libsystemd-daemon.so.0:
      http://packages.ubuntu.com/search?searchon=contents&keywords=libsystemd&mode=filename&suite=xenial&arch=any
      There is libsystemd but not libsystemd-daemon.
      It's the same with Ubuntu Yakkety and Zesty.

      The bintar package is built on Trusty. Trusty does have libsystemd-daemon:

      http://packages.ubuntu.com/search?searchon=contents&keywords=libsystemd&mode=filename&suite=trusty&arch=any

      I guess this is why bintar is linked against it.

      I think it is still a bad experience that bintar package cannot be used on a very popular system, latest LTS of probably the most popular distro.

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. MDEV-13090 Deprecated libsystemd library linked to Mariadb 10.1.24 mysqld binary

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          Task - A task that needs to be done. MDEV-22672 10.5 bintar builders

          • Blocker - Blocks development and/or testing work, production could not run.
          • Closed

          Activity

            Ascending order - Click to sort in descending order
            View 7 older comments
            serg Sergei Golubchik added a comment - - edited

            For every distro where build binaries. There are rpm2targz and rpm2targz tools, your release scripts can repackage rpm/deb into bintars. Or we can do it in buildbot even. Build packages and immediately create a bintar out of _CPack_Packages. It won't even need any2targz, only tar and gzip.

            The question is how to offer them without overwhelming the user. I think repositories download page could be a good fit

            serg Sergei Golubchik added a comment - - edited For every distro where build binaries. There are rpm2targz and rpm2targz tools, your release scripts can repackage rpm/deb into bintars. Or we can do it in buildbot even. Build packages and immediately create a bintar out of _CPack_Packages . It won't even need any2targz, only tar and gzip. The question is how to offer them without overwhelming the user. I think repositories download page could be a good fit
            dbart Daniel Bartholomew added a comment -

            You mean the repo config tool? Yes, putting something there would probably work fine.

            dbart Daniel Bartholomew added a comment - You mean the repo config tool ? Yes, putting something there would probably work fine.
            serg Sergei Golubchik added a comment -

            As we've later discussed, this trick won't work, because the tarball will have deb (or rpm) file layout.

            To create a bintar with the correct bintar file layout, we have to build it that way.

            Which, probably, means we should move systemd bintar builder from trusty to xenial.

            serg Sergei Golubchik added a comment - As we've later discussed, this trick won't work, because the tarball will have deb (or rpm) file layout. To create a bintar with the correct bintar file layout, we have to build it that way. Which, probably, means we should move systemd bintar builder from trusty to xenial.
            dbart Daniel Bartholomew added a comment -

            I've added kvm-bintar-xenial-amd64 and kvm-bintar-xenial-x86 builders to buildbot. Assuming they work fine I will next remove the corresponding kvm-bintar-trusty* builders and switch the release scripts to use the new builders for the systemd bintar tarballs in future releases.

            dbart Daniel Bartholomew added a comment - I've added kvm-bintar-xenial-amd64 and kvm-bintar-xenial-x86 builders to buildbot. Assuming they work fine I will next remove the corresponding kvm-bintar-trusty* builders and switch the release scripts to use the new builders for the systemd bintar tarballs in future releases.
            dbart Daniel Bartholomew added a comment -

            AFAIK This was fixed a while back with some changes to the systemd bintar builder.

            dbart Daniel Bartholomew added a comment - AFAIK This was fixed a while back with some changes to the systemd bintar builder.

            People

              dbart Daniel Bartholomew
              psergei Sergei Petrunia
              Votes:
              2 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.