On Wed, Jan 25, 2012 at 08:08:06AM -0800, Andrew Pollock wrote: > On Tue, Jan 24, 2012 at 10:28:18PM -0800, Russ Allbery wrote: > > Andrew Pollock <[email protected]> writes: > > > > > I just got onto the git-pbuilder bandwagon, and was briefly confused as > > > to where my resulting build went, because when I use pdebuild, the > > > results wind up in the default location of /var/cache/pbuilder/result, > > > and I'm quite happy with that. > > > > > git-pbuilder seems to forcibly supply a "--buildresult .." with no way > > > to override that. > > > > That's because the way this normally works is that git-buildpackage runs > > git-pbuilder and expects that behavior, because that means the build ends > > up in build-area (or whatever you have configured). > > So historically I didn't know about git-pbuilder and run git-buildpackage > something like this: > > git-buildpackage --git-builder="pdebuild --debbuildopts '-i\.git -I.git' -- > --basepath /var/cache/pbuilder/base-unstable.cow" You can run git-pbuilder with GIT_PBUILDER_AUTOCONF set which will avoid passing --buildresult. When using git-buildpackage that means --git-no-pbuilder-autoonf (which is available in gbp from experimental). Cheers, -- Guido
-- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
