Hi,
On 31/10/2016 08:01, Lucas Nussbaum wrote:
On 29/10/16 at 11:14 +0200, Julien Puydt wrote:
Hi,
I tried to "pbuilder create" a new base.tgz, but it still had tzdata and
lsb-base, so I had to "pbuilder login --save-after-login" and remove them by
hand using "dpkg --purge" (then "apt-get autoremove" that did nothing). I
still had no problem building node-es6-promise.
How can I get the clean, minimal and up-to-date chroot you mention in your
report?
Hi Julien,
You can install debfoster in the chroot, and then run
debfoster -o UseRecommends=no -o MaxPriority=required
to clean up the chroot from non-essential packages.
I made several tests with your debfoster line :
(*) if I let dpkg-dev go, pbuilder can't even try to compile packages
because it's missing dpkg-architecture
(*) if I let gcc go, dpkg-architecture can't determine the system type ;
(*) if I let aptitude go, pbuilder can't install the build deps ;
(*) if I let build-essential go, pbuilder will install the build deps,
but dpkg-buildpackage will fail because of unmet build dependencies (on
build-essential: native !)
So I kept apt, aptitude and build-essential : no problem building
node-es6-promise with pbuilder.
Since I really wanted to fix that bug, I thought I could get a smaller
chroot by doing things by hand -- after all I have less needs than
pbuilder : using debfoster I kept only apt, then installed nano so I
could edit the sources.list (enable the deb-src line) and apt-get
update, then installed the build-dep for node-es6-promise, apt-get
source node-es6-promise, then dpkg-buildpackage -b -us -uc... no problem!
I don't manage to reproduce the failure, and I don't know what I could
try next. Do you have more ideas?
Snark on #debian-js
