[Pkg-gtkpod-devel] Missing commits for libplist

[Boyuan Yang]

在 2019-01-07一的 15:48 +0100，Yves-Alexis Perez写道：
> On Mon, 2019-01-07 at 09:46 -0500, Boyuan Yang wrote:
> > > By the way, right now I'm doing a git merge of the manually tagged stuff
> > > in
> > > the upstream branch, but it would apparently be possible to do a gbp
> > > import-
> > > orig --uscan provided debian/watch has the correct stuff in it.
> > 
> > I'd recommend using gbp import-orig --uscan --pristine-tar to
> > automatically
> > generate pristine-tar branch from upstream tarballs when applicable.
> 
> Unfortunately upstream doesn't really produce tarballs anymore. I can
> generate
> fake tarballs myself but if everything is in git that doesn't really makes
> sense.

That's fine. Whenever upstream makes a tag, we may retrieve the auto-generated 
tarball from github mirror. Before that I guess we will have to stick with
git-generated tarballs anyway.

> > >   Do you have an
> > > idea of the right syntax for that?
> > 
> > Once upstream tags a new version and we decide to use upstream-provided
> > tarball, I guess it's just some standard stuff as documented in uscan(1).
> > Is
> > there any certain concerns with it?
> 
> I meant to actually import a new orig to pristine-tar using only a git tag.

If upstream is not making tags (thus not providing tarballs), we can only use
pristine-tar(1) tool to manually import a (generated) tarball into pristine-
tar branch. Try "gbp export-orig" or something like that.

--
Thanks,
Boyuan Yang