On 29 Jan 2017, at 09:27, Otto Kekäläinen <[email protected]> wrote: > Hello! > > 2017-01-28 3:32 GMT+02:00 James Clarke <[email protected]>: >> Are you using a very old chroot? You need dpkg-dev (>= 1.18.11) to support >> quadruplets in the Architecture field, though that was uploaded on the 6th >> November... > > No TokuDB in unstable now: > https://packages.debian.org/unstable/mariadb-plugin-tokudb > This problably due to me uploading binaries, and as other no than > amd64 will build TokuDB, and the amd64 had no reason to trigger a > rebuild, so only my binaries (without TokuDB) are in the repositories > now. > > I am using pbuilder to build, and I updated the chroots just a few > days ago (http://labs.seravo.fi/~otto/debian/update-chroots.sh), so it > is unlikely the dpkg versio was old, unless the pbuilder update is > somehow broken. If it worked for you on barreire, then I don't know > what caused it here.
Yeah, I'm not sure what's wrong with your setup. I would suggest checking the version of dpkg-dev inside your chroot, since that should be the only thing determining whether the package is built. Does the build log show it building the TokuDB sources (even though it didn't build a package)? Did the build log include the DEB_HOST_ARCH_ABI in the dpkg-architecture dump? Regards, James
