On 02/01/2017 08:42 PM, James Clarke 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 > to check the package builds, you're not actually building any binary packages; > you should instead use the new --source-only-changes option, which will build > binary packages but also generate a source-only changes.
I first build the binary packages to test them. Only once everything is fine I build the source package for uploading, using gbp's magic to git tag the release. This workflow saves me from accidentally uploading/pushing something wrong, and at the same time I'm able to change minor things and release them, without having to rebuild the binary packages (which takes some time for Wine). Further it's just laziness: use the same command for all kinds of builds, just change one or two options. So this is a small plea to reconsider this decision for source-only. But of course, I can definitely set up something working again with your explanations and the new --source-only-changes, thanks! > For binary-indep-only, I assume you are using -A, which git-pbuilder sees as a > dpkg-buildpackage option and passes on to cowbuilder via --debbuildopts. > However, cowbuilder/pbuilder do not look at debbuildopts to determine what > kind > of build is being done; they have their own flags. Please use > --binary-arch/--binary-indep as per the pbuilder man page (you may need to use > --git-pbuilder-options=--binary-indep to get it passed through properly). Yes, I used -A. Funnily, the similar command with -B worked (building only the arch binaries, but not the indep ones). Wow, I admit I didn't have a look at the pbuilder manpage for a long time, but indeed this is very well described there. With this new knowledge I'm totally fine with this change. Greets jre
