[debian-mysql] Bug#852709: Bug#852709: Patch

[James Clarke]

On 29 Jan 2017, at 15:24, Otto Kekäläinen <otto at debian.org> wrote:
> 2017-01-29 17:12 GMT+02:00 James Clarke <jrtc27 at debian.org>:
>> 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?
> 
> 
> http://labs.seravo.fi/~otto/debian/mariadb-10.1-sid-amd64/mariadb-10.1_10.1.21-5_amd64.build-d237cd1-pbuilder.log
> 
> dpkg-architecture: error: DEB_HOST_ARCH_ABI is not a supported variable name
> 
> 
> So pbuilder update has stopped working or something. I shall delete
> the whole sid chroot and create a new one from scratch.

That's coming from debian/rules clean being run outside the chroot to build the
source package, before it gets copied into the chroot. It doesn't seem fatal
though, and shouldn't be needed for the clean target. You have a version of
dpkg-dev inside the chroot which knows about DEB_HOST_ARCH_ABI, since there's
DEB_HOST_ARCH_ABI=base printed later on.

TokuDB was definitely built and installed:

> -- Installing: /tmp/buildd/mariadb-10.1-10.1.21/debian/tmp/usr/lib/x86_64-linux-gnu/mariadb18/plugin/ha_tokudb.so

For some reason dh_builddeb (which delegates to Debhelper::Dh_Lib to get the
packages to build) didn't think it should build the package. Very strange...

Regards,
James