Comment 7 for bug 1606102

I have done a preliminary backport. Please can you test on ppc64el to see if this fixes the problem? My backport is at ppa:racb/experimental.

Note that armhf FTBFS for some reason, so this will need further investigation since it did work in Xenial previously. It's not clear to me from the build log whether this is something I introduced in my backport, or there is some other reason for the failure.

Also, I haven't looked at addressed the situation in Zesty at all, and this will need resolving before any SRU.

Backport notes:

There are two upstream branches: codership's 3.x and mariadb-3.x.
mariadb-3.x regularly merges in codership's 3.x branch. This merging
happens in only one direction; effectively codership's branch is
mariadb-3.x's upstream. mariadb-3.x's branch is what is packaged in this
source.

Two relevant commits are 0e815d9 and 22c4a52. 0e815d9 adds ppc64el
support, only exists in the mariadb-3.x branch, and is what is
backported here. 22c4a52 adds s390x support and exists in both branches.
The changes introduced by the two commits first appear together in
6896615.

Cherry-picking 0e815d9 on its own results in a merge conflict because of
the changes introduced by 22c4a52. Since this conflict was already
resolved by mariadb-3.x upstream in 6896615, this backport resolves the
conflict in exactly the same way.