> > On armel, the control files correctly contain no Built-Using field.
> I have not noticed the issues on armel, just armhf (with 0.0.5 or 0.0.6)
> and arm64 (with 0.0.6).
I have tried again on an armhf porterbox, all works as expected.
> > Could you please describe your build environment?
> I use sbuild with unshare chroot mode...
Thanks for the explanations. If I understand correctly, sbuild needs
root permissions at least to create the chroot, so I cannot run it on
a porterbox.
Can you please try
# dh_builtusing -v
# cat debian/*.substvars
This should work in a clean source tree, without spending time building.
(arm64 or armhf, the symptoms differ but the cause seems the same)
The expected output on armhf is:
In package u-boot-sunxi, substvar dh-builtusing:arm-trusted-firmware +=
disabled-by-restriction
In package u-boot-sunxi, substvar dh-builtusing:crust-firmware +=
disabled-by-restriction
In package u-boot-rockchip, substvar dh-builtusing:arm-trusted-firmware
+= disabled-by-restriction
dh-builtusing:arm-trusted-firmware=disabled-by-restriction (= 0)
dh-builtusing:arm-trusted-firmware=disabled-by-restriction (= 0)
dh-builtusing:crust-firmware=disabled-by-restriction (= 0)
