On 21/08/15 13:21, Danny Edel wrote: > Once sbuild is setup Just to clarify. In this use case (using sbuild as close to buildd as possible), the steps labeled "for personal use" in https://wiki.debian.org/sbuild#Configuration are *not* what we want.
The Source package will be created by debuild -S on the host machine, and sbuild will *only* build the binary. So the entire (!) series of installation steps is: * (root) apt-get install sbuild * (root) mkdir -p /root/.gnupg * (root) sbuild-update --keygen * (root) sbuild-adduser $YOURUSERNAME logout-relogin or use "newgrp sbuild" in your current shell. Now to create the chroots: * (root) sbuild-createchroot --make-sbuild-tarball=/var/lib/sbuild --arch amd64 /sid-amd64.tar.gz sid $(mktemp -d) http://httpredir.debian.org/debian * (root) sbuild-createchroot --make-sbuild-tarball=/var/lib/sbuild --arch i386 /sid-i386.tar.gz sid $(mktemp -d) http://httpredir.debian.org/debian Thats it. Note that you can also use "wheezy" or "jessie" if you plan on testing backporting to those. >From now on, "sbuild --dist sid --arch amd64 path/to/my.dsc" works. This will implicitly call dist-upgrade, install build dependencies, copy files around and work its magic while you're enjoying your coffee. (Yes, this really can take a while). I would recommend setting up a local (partial) debian mirror to speed up the package fetching step, but I've gotten weird "500 invalid header" errors when I use apt-cacher-ng, so I'm not recommending this for now. The only sbuild configuration line I *strongly* suggest is $environment_filter = [ ]; This will ensure that no CXXFLAGS= or similar from your working environment contaminate the clean chroot. - Danny
