On 2024-03-24, nicolas.bouleng...@free.fr wrote:
> Hello.
> I failed to reproduce the issue on a porterbox.
>
> On arm64:
> # dpkg-source -x u-boot_2024.01+dfsg-3.dsc
> # cd u-boot_2024.01+dfsg
> # patch -p1 < ../b8d394100d6f858c0e80786f7087f96c11d698c3.diff
> # DEB_BUILD_PROFILES='pkg.uboot.notools 
> pkg.uboot.platform.a64-olinuxino' fake\
> root debian/rules binary-arch
> dpkg-gencontrol writes no warning
> debian/u-boot-{rockchip,sunxi}/DEBIAN/control contain the expected 
> Built-Using\
>   fields
>
> 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).


> Could you please describe your build environment?

I use sbuild with unshare chroot mode...

Essentially, I build a tarball using a script like this:

  
https://salsa.debian.org/reproducible-builds/sbuild-unshare-reprotest/-/blob/main/mm-sbuild

Then call sbuild from the source directory:

  sbuild --chroot-mode=unshare -d UNRELEASED -c sid-armhf --arch=armhf \
    --no-arch-all --arch-any --source --no-run-lintian --no-clean-source \
    
--profiles=pkg.uboot.notools,pkg.uboot.subarch.rockchip,pkg.uboot.subarch.sunxi

Seems to behave the same with or without the build profiles, but using
the build profiles reduces the set of built packages to ones that
trigger the issue...

I use the u-boot git repository and cherry-pick
b8d394100d6f858c0e80786f7087f96c11d698c3 into current debian/latest
commit b09ea5f73b440d9f78e1de2b9b9e583ba4bc2541 tag
debian/2024.01+dfsg-3 and then bump debian/changelog appropriately.

I am running these builds on a honeycomb lx2 (arm64), which has support
for running armhf natively as well.

Just re-ran the tests again, and they still fail for me:

  
https://people.debian.org/~vagrant/dh-builtusing-issues/u-boot_2024.01+dfsg-4~0~20240324~0_arm64-2024-03-24T20:22:28Z.build.zst
  
https://people.debian.org/~vagrant/dh-builtusing-issues/u-boot_2024.01+dfsg-4~0~20240324~0_armhf-2024-03-24T20:21:58Z.build.zst

live well,
  vagrant

Attachment: signature.asc
Description: PGP signature

Reply via email to