Bug#881640: pbuilder: --preserve-buildplace is broken with pbuilder-satisfydepends-classic

Daniel Schepler dschepler at gmail.com
Mon Nov 13 19:32:20 UTC 2017


Package: pbuilder
Version: 0.229
Severity: normal

Since a recent upload, pbuilder copies and extracts the source package
in the chroot before invoking the satisfydepends script.  With the
combination of pbuilder-satisfydepends-classic and
--preserve-buildplace, this breaks things because the chroot "cache
directory" is no longer left in its initial (clean) state.

This especially breaks things with my setup, which contains a
post-unpack hook which relies on there being exactly one source
package in /build.  (The setup, which was the original use case I had
in mind in implementing --preserve-buildplace in the first place, is a
script to maintain a "dogfooding" local mirror of bootstrapped
packages, and run a loop that goes through all the packages that
haven't been bootstrapped so far trying to build them all.  So, the
--preserve-buildplace is essential to get any kind of speed when most
of the packages don't yet have satisfiable Build-Depends from the
bootstrapped set.)

(It would also be nice if pbuilder-satisfydepends-apt would support
--preserve-buildplace by returning exit code 2 if "apt-get -s
build-dep" fails.  That would be so much faster than
pbuilder-satisfydepends-classic.)
-- 
Daniel Schepler



More information about the Pbuilder-maint mailing list