Package: dh-builtusing Version: 0.0.5 Severity: normal Control: affects -1 u-boot X-Debbugs-Cc: vagr...@debian.org
u-boot recently switched to dh-builtusing, but it fails with
architecture-specific Built-Using entries in packages that do not have
the same Built-Using dependencies across architectures, e.g. for an
armhf build with arm64 specific Built-Using entries:
dpkg-gencontrol: warning: Built-Using field of package u-boot-rockchip:
substitution variable ${dh-builtusing:arm-trusted-firmware} used, but is not
defined
dpkg-gencontrol: warning: can't parse dependency [arm64]
dpkg-gencontrol: error: parsing package 'u-boot-rockchip' Built-Using field:
[arm64]
...
dpkg-gencontrol: warning: Built-Using field of package u-boot-sunxi:
substitution variable ${dh-builtusing:arm-trusted-firmware} used, but is not
defined
dpkg-gencontrol: warning: Built-Using field of package u-boot-sunxi:
substitution variable ${dh-builtusing:crust-firmware} used, but is not defined
dpkg-gencontrol: warning: can't parse dependency [arm64]
dpkg-gencontrol: error: parsing package 'u-boot-sunxi' Built-Using field:
[arm64],
[arm64],
The dh-builtusing manpage suggests this should work, but results in an
invalid Built-Using field:
Built-Using: [arm64]
It seems the substitution variable is correctly empty, but still
leaves the architecture qualifier in the result...
I tried working around this by leaving out the architecture qualifier,
but then failed differently:
dpkg-query: no packages found matching arm-trusted-firmware
dh_builtusing: error: dpkg-query -Wf
"\${source:Package},\${source:Version},\${Architecture}\" arm-trusted-firmware
returned exit code 1
make: *** [debian/rules:63: binary-arch] Error 25
Leaving out the architecture qualifiers worked before switching to
dh-builtusing, though it did issue warnings in the build log about empty
variables.
Thanks for dh-builtusing, despite this hopefully small bump along the
road!
live well,
vagrant
signature.asc
Description: PGP signature
