It's been discussed before (without much result), but I don't think we had it filed. Assigning to Otto to clarify what we should do about it, since now at least p8 trusty build does not work in buildbot.

If you do manual builds, you can run dpkg-buildpackage -d and the build will proceed even if the required dependencies are not met.

If you want to customize that certain platforms have different control files, you could do something similar as is already done in the autobake-deb.sh file regarding the libcrypto dependency.

Customizing and maintaining the control file for various different platforms and OSes doesn't sound very attractive. Debian and Ubuntu, and individual versions of each, might very well have different build dependencies, right? Maybe that's less of an issue than I'd expect.

otto, I'm afraid I don't know what you're referring to with "the libcrypto dependency". I don't see any mention at all of "crypto" anywhere in the debian/ subdirectory of the 10.1 branch.

Or maybe you're referring instead to libcrack2, where the autobake script does some brute-force apt + sed gymnastics to edit the control file? If that's the recommended approach, then I guess it's the one we'll have to use. It seems like there should be something a lot more flexible than this, though.

MDEV-3809 could be a solution to this (and many other) packaging problems.

kolbe Yes, I meant the libcrack2 hack. That is the easiest way to customize the debian/* contents at build time if there is some exceptions to the packaging, which otherwise very nicely works on all Debian/Ubuntu releases we want to support.

serg, I don't disagree with you, but I think otto does not like the idea of using CPack, especially for Debian packaging. Anyway, the discussion about that broader issue can happen elsewhere.

libjudy-dev is available on all relevant platforms and mariadb-10.0 in Debian with libjudy-dev as a build dependency works well: https://buildd.debian.org/status/package.php?p=mariadb-10.0