Re: extracting upstream source.
Package: dgit
Version: 3.12
Peter Green writes ("extracting upstream source."):
> As part of my dgit based autoforwardporter I want to add a script that will
> de-fuzz patches with fuzz and remove patches that cannot be applied.
>
> To do this I need the "upstream" source tree. However the process of
> extracting the upstream source is quite fiddly, there may be multiple
> tarballs to deal with, tarballs may or may not have a top-level directory
> that needs to be removed from the paths etc.
>
> Both dpkg-source ("commit" and "build")and dgit (quilt fixup) clearly extract
> the upstream source tree as part of their processing, so the code to do it
> already exists but i'm not sure if there is a convenient way to access it.
dgit often has "something like" the upstream source tree as a git tree
object. dgit should provide a way for you to get at it.
Ian.
--
Ian Jackson <ijack...@chiark.greenend.org.uk> These opinions are my own.
If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.
___
vcs-pkg-discuss mailing list
vcs-pkg-discuss@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/vcs-pkg-discuss
Re: extracting upstream source.
On Tue, Jul 25, 2017 at 03:55:08PM +0100, Ian Jackson wrote:
> Ian Jackson writes ("Re: extracting upstream source."):
> > dgit often has "something like" the upstream source tree as a git tree
> > object. dgit should provide a way for you to get at it.
>
> This is now #869675.
For our Ubuntu git work, we're using pristine-tar branches to provide
these.
signature.asc
Description: PGP signature
___
vcs-pkg-discuss mailing list
vcs-pkg-discuss@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/vcs-pkg-discuss
Re: extracting upstream source.
Ian Jackson writes ("Re: extracting upstream source."):
> dgit often has "something like" the upstream source tree as a git tree
> object. dgit should provide a way for you to get at it.
This is now #869675.
Ian.
--
Ian Jackson <ijack...@chiark.greenend.org.uk> These opinions are my own.
If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.
___
vcs-pkg-discuss mailing list
vcs-pkg-discuss@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/vcs-pkg-discuss
extracting upstream source.
As part of my dgit based autoforwardporter I want to add a script that will
de-fuzz patches with fuzz and remove patches that cannot be applied.
To do this I need the "upstream" source tree. However the process of extracting
the upstream source is quite fiddly, there may be multiple tarballs to deal with,
tarballs may or may not have a top-level directory that needs to be removed from the
paths etc.
Both dpkg-source ("commit" and "build")and dgit (quilt fixup) clearly extract
the upstream source tree as part of their processing, so the code to do it already exists but i'm
not sure if there is a convenient way to access it.
Any hints?
___
vcs-pkg-discuss mailing list
vcs-pkg-discuss@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/vcs-pkg-discuss
