On Wed, Mar 27, 2019 at 09:10:39AM +0100, Olivier Sallou wrote: > > > During a rebuild of all packages in buster (in a buster chroot, not a > > sid chroot), your package failed to build on amd64. > > I just did a try on buster. > > It succeeded first time, not on a second rebuild (with same error).
I also was able to reproduce the error in a buster chroot (at first try). I was thinking whether --no-parallel might have helped as well since this is a usual cause for non-predictable racing conditions. I actually succeeded with diff --git a/debian/rules b/debian/rules index 66f96f8..8b15674 100755 --- a/debian/rules +++ b/debian/rules @@ -15,7 +15,7 @@ override_dh_auto_build: mv $${script} cnvkit-$${script%%.py}; \ done; \ fi - dh_auto_build + dh_auto_build --no-parallel cd scripts && for script in cnvkit-*; do \ mv $${script} $${script##cnvkit-}.py; \ done > I fixed and tested on buster with new patch d/patches/controldir. Git is > up-to-date and in UNRELEASED state. Seems your fix goes more to the root of the issue so we should go with this. > As we are in freeze, should we ask release team to unblock transition > and then push to unstable? Yes, please do so. > Though not a bug issue, bug could be forwarded upstream as it raises an > error to use an existing dir. Probably. Kind regards Andreas. -- http://fam-tille.de