Hi, On Wed, Sep 03, 2025 at 12:12:55PM -0700, Keith Packard wrote: > > > Makes sense. We should also amend `git-pbuilder` slightly to read a > > `GIT_PBUILDER_HOST_ARCH` to be consistent with what we do for > > `--git-arch`. > > Yup, consistency is good. > > > Am I assuming correctly that you're using plain > > /var/cache/pbuilder/base.cow/ / /var/cache/pbuilder/base-$DIST.cow for > > that or do you have special chroots setup for that purpose? > > I happen to be using a special chroot for testing, but it's not required -- > you
That's what I suspected, thanks for confirming! > can have a multiarch base.cow and use that to create both native and > cross built packages. I created my chroot using this command: I'm clear on that part. The question is how we want it to work. For thinks like --git-arch and --git-dist we have all the chroot setup integrated into git-builder and we want to do the same for the --git-host-arch variant so it becomes easy to use out of the box as well. So maybe using dirs like `base-sid-host-$arch` or similar could work to tell things apart and then … > > sudo cowbuilder create \ > --basepath /var/cache/pbuilder/base-cross.cow \ > --debootstrap mmdebstrap \ > --debootstrapopts --architectures=amd64,arm64 \ > --debootstrapopts --skip=output/dev \ > --debootstrapopts --variant=buildd \ > --debootstrapopts --include=ca-certificates …we could add something like the above to git-builder to create those chroots. So it seems this becomes a bit more complicated than just adding the option but looks worthwhile to have. Cheers and thanks for the details! -- Guido > > Helmut suggested that I add > > --debootstrapopts > --include=crossbuild-essential-arm64,libc6-dev:arm64,libstdc++-dev:arm64 > > to speed up cross builds. Thanks for reviewing my bug report! > > -- > -keith
