Le mardi 30 juin 2026 à 15:33 +0200, Stéphane Glondu a écrit : > On Tue, 30 Jun 2026 15:12:04 +0200 Julien Puydt > <[email protected]> > wrote: > > Andrey Rakhmatullin suggested to use: > > mmdebstrap --chrooted-customize-hook=bash unstable /dev/null > > > > for the bootstrap test, so now I can say it fails in a chroot too. > > For the record, I did (in the shell given by the command above): > > cd tmp > apt-get install git-buildpackage pristine-tar devscripts > adduser sbuild > runuser -u sbuild bash > gbp clone https://salsa.debian.org/ocaml-team/coq-hammer.git > cd coq-hammer/ > gbp import-orig --uscan > > and it works for me. > > > So in short: > > - it fails on my account on my box ; > > - it fails on a new account on my box ; > > - it fails in a chroot on my box... > > > > and I still don't know why. > Weird...
Oh, I tried again following your line and it worked. The problem is that I didn't check the error message, only that it failed. But then I realized I had only done "apt install git-buildpackage" -- no pristine-tar! So now I'm having the following pretty interesting situation in the chroot: - apt install git-buildpackage - checkout the elpi and coq-hammer packages (both from salsa/ocaml- team) - try to gbp import-orig --uscan in both - coq-hammer works, elpi fails stating pristine-tar is not available - now apt install pristine-tar - now elpi works. How could that work with coq-hammer in a pristine-tar-less chroot ? Why does it fail with pristine-tar on my box ? I'm so confused... JP
