On Wed, Feb 21, 2018 at 8:32 PM, Ian Jackson
<ijack...@chiark.greenend.org.uk> wrote:
> Felipe Sateler writes ("Bug#891033: dgit: Please integrate with
> pristine-tar"):
>> It would be great if dgit would detect a pristine-tar enabled repo, and
>> in that case try to checkout the upstream tarball if it is not present
>> in `..`.
>
> Hi. I'm not sure exactly when you think it should do this.
Sorry for being too terse.
>
> Do you mean when the user says "dgit clone" ? Or do you mean when
> building a source package ?
When building a source package. In my (gbp-based) workflow, I
don't always have the current tarball in `..`, for the following
reasons:
1. I use gbp's export-dir option to run builds in a tmpfs, so the
tarball lives somewhere in /tmp.
2. Even if not doing that, I might have pulled a git tree with an
upstream tarball imported by a teammate. Pristine-tar avoids hash
mismatch problems by ensuring we both use the same tarball.
Note that I currently faced this error when using `dgit push-source`.
Perhaps other build options do not have this problem due to gbp
integration (gbp already extracts the tarbal when it needs to).
> It's possible that dgit could be extended somehow in these directions
> but I don't think it's entirely trivial, depending what is wanted.
/me hopes it is not difficult.
--
Saludos,
Felipe Sateler
