Seems the fix was released some time ago but the corresponding changelog didn't
close this bug.
On Wed, Jan 25, 2012 at 11:14:02AM -0800, Russ Allbery wrote:
> Andrew Pollock writes:
> > On Wed, Jan 25, 2012 at 08:09:01PM +0100, Guido Günther wrote:
>
> >> For what it's worth I'm using .. without using --git-export. I dropped
> >> the extra --git-export step ages ago but I'm happy to find t
Andrew Pollock writes:
> On Wed, Jan 25, 2012 at 08:09:01PM +0100, Guido Günther wrote:
>> For what it's worth I'm using .. without using --git-export. I dropped
>> the extra --git-export step ages ago but I'm happy to find the files
>> generated by git-pbuilder where the would also end up when u
On Wed, Jan 25, 2012 at 08:09:01PM +0100, Guido Günther wrote:
> On Wed, Jan 25, 2012 at 10:52:42AM -0800, Russ Allbery wrote:
> [..snip..]
> > Another interesting option may be to change git-pbuilder to stop setting
> > the directory into which to store the results and change git-buildpackage
> >
On Wed, Jan 25, 2012 at 10:52:42AM -0800, Russ Allbery wrote:
[..snip..]
> Another interesting option may be to change git-pbuilder to stop setting
> the directory into which to store the results and change git-buildpackage
> to pass in a flag saying to use .. iff --git-export-dir was specified.
F
Andrew Pollock writes:
> I'm not convinced that will work, but I'll give it a try. The man page
> says
> "Export the current branch head (or the treeish object given via
> --git-export to directory before building."
Yeah, I noticed; the interaction between that and where the built Git
packages
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 writes:
> >
> > > I just got onto the git-pbuilder bandwagon, and was briefly confused as
> > > to where my resulting build went, because when I use p
On Tue, Jan 24, 2012 at 10:28:18PM -0800, Russ Allbery wrote:
> Andrew Pollock 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/pbu
Andrew Pollock 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
Package: git-buildpackage
Version: 0.5.32
Severity: wishlist
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
t
10 matches
Mail list logo
