[DRE-maint] Bug#871737: ruby-em-synchrony: uses mariadb features at build-time, should build-dep on mariadb directly

[Steve Langasek]

Package: ruby-em-synchrony
Version: 1.0.5-2
Severity: important
Tags: patch
User: ubuntu-devel at lists.ubuntu.com
Usertags: origin-ubuntu artful ubuntu-patch

Dear maintainers,

The latest version of ruby-em-synchrony fails to build in Ubuntu, because it
invokes mysql_install_db --force --skip-name-resolve as part of the build,
but these are options that are only understood by the mariadb implementation
of mysql_install_db and Ubuntu's default-mysql-server is configured to mysql
instead of mariadb.

Since this server is only needed at build-time for testing, I don't think it
makes sense to put much effort into making debian/start_services_and_run.sh
implementation-agnostic.  Instead, I think ruby-em-synchrony should just
build-depend on mariadb-server directly.

I've uploaded this change to Ubuntu, using the attached trivial patch. 
Please consider including this change in Debian as well.

Cheers,
-- 
Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
Ubuntu Developer                                    http://www.debian.org/
slangasek at ubuntu.com                                     vorlon at debian.org
-------------- next part --------------
diff -Nru ruby-em-synchrony-1.0.5/debian/control ruby-em-synchrony-1.0.5/debian/control
--- ruby-em-synchrony-1.0.5/debian/control	2016-12-18 17:17:19.000000000 -0800
+++ ruby-em-synchrony-1.0.5/debian/control	2017-08-10 16:43:22.000000000 -0700
@@ -7,7 +7,7 @@
 Build-Depends: debhelper (>= 9),
                gem2deb,
                memcached,
-               default-mysql-server | virtual-mysql-server,
+               mariadb-server,
                procps,
                redis-server,
                ruby-activerecord,