Source: dgit Version: 13.10 Hello,
The quilt-gbp-build-modes-sbuild and sbuild-gitish tests fail for me
when run under tests/run-all. Hacking that script such that jcpus=-j1
avoids the issue.
I am not sure that the problem is that my sbuild setup actually can't do
the parallelism. This problam has only recently emerged, possibly with
the upgrade to trixie -- but I did make *some* changes to my sbuild
setup relatively recently.
Looking in the test output:
--8<---------------cut here---------------start------------->8---
+ build
+ eval ' git clean -xdf
sbuild -v -d sid -A --no-clean-source \
--dpkg-source-opts='\''-Zgzip -z1 --format=1.0 -sn'\'''
++ git clean -xdf
++ sbuild -v -d sid -A --no-clean-source '--dpkg-source-opts=-Zgzip -z1
--format=1.0 -sn'
The Debian buildds switched to the "unshare" backend and sbuild will default to
it in the future.
To start using "unshare" add this to your `~/.config/sbuild/config.pl`:
$chroot_mode = "unshare";
If you want to keep the old "schroot" mode even in the future, add the
following to your `~/.config/sbuild/config.pl`:
$chroot_mode = "schroot";
$schroot = "schroot";
dpkg-source: warning: native package version may not have a revision
dpkg-source: warning: source directory 'example' is not
<sourcepackage>-<upstreamversion> 'example-1.1'
dpkg-source: info: using source format '1.0'
dpkg-source: info: building example in example_1.1-1.tar.gz
dpkg-source: info: building example in example_1.1-1.dsc
sbuild (Debian sbuild) 0.89.3 (07 June 2025) on zephyr.silentflame.com
--8<---------------cut here---------------end--------------->8---
This text about the unshare backend is suppressed if you have the
suggested $chroot_mode="schroot" and $schroot="schroot" in your
~/.config/sbuild/config.pl -- which I do.
This makes me think that the test suite in these two particular tests is
somehow neutering my ~/.config/sbuild/config.pl ?
I can't see any code to do that, but is that how it is meant to work?
--
Sean Whitton
signature.asc
Description: PGP signature
