On 23 Feb 2017, at 16:04, Andreas Beckmann <a...@debian.org> wrote: > On Wed, 1 Feb 2017 19:42:26 +0000 James Clarke <jrt...@debian.org> wrote: >> For source-only builds, I don't understand why you would want to perform the >> build in a chroot. You already have to be able to build the source package >> outside the chroot, which then gets copied into the chroot, unpacked and a >> new >> source package is built; why not use the first source package? If your aim is > > I want to build the source package in the distro where it's going to be > uploaded, using tools from only that distro. This may make a difference > if I get a .debian.tar.gz or .debian.tar.xz (or .diff.gz vs. .diff.xz ?). > And I want to build the source package in a clean minimal chroot, not > upload something built in my non-minimal mixed-distro host :-) > > So far I always used --debbuildopts -S for a final source-only build > that was going to be uploaded (after doing testing binary builds).
Why not use --source-only-changes and upload the _source.changes from your final test binary build? > --binary-indep is not working as a "workaround" if the package builds no > arch:all packages. Regards, James