On 16/10/14 18:01, Tristan Seligmann wrote:
> The purpose of pristine-tar is the same whether you base it on a
> revision fetched from upstream, or a revision created by
> git-import-orig or a similar tool
... or a revision created by "git-import-orig
--upstream-vcs-tag=v1.2.3", which has the contents of the tarball as its
"tree", and two parent commits (a "pseudo-merge"): the upstream VCS tag
v1.2.3, and the previous tarball. This seems like the best of both
worlds, assuming IRC/email commit bots filter out the upstream-only
commits in its ancestry.
> Alternatively, if you will never generate the upstream source from the
> git repository, then you avoid this problem, but then building a
> particular package version may require manually fetching the correct
> tarball from the archive / snapshot.debian.org if they are no longer
> available from the original source
That's assuming "the correct tarball" is even in the archive. For
un-uploaded packages for which a sponsored upload was requested, you
need to obtain a compatible tarball in some out-of-band way. For
packages in NEW, it's worse: you need to obtain precisely the same
tarball that's already in NEW in some out-of-band way.
S
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/543fff3c.60...@debian.org
