[Pkg-gtkpod-devel] Missing commits for libplist

Yves-Alexis Perez corsac at debian.org
Mon Jan 7 14:48:35 GMT 2019


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

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.
> 
> >   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.

Regards,
- -- 
Yves-Alexis
-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAlwzZsMACgkQ3rYcyPpX
RFvlQAf6AgasKprswV7Cu+9ZUPb3W5WZ3gaYG53nPL/BgmgOoxdPZ5CrWw+4NOMd
3Q7/UpNk8H6J3NdIGhUwpjblyDutbc6akd6HoSTYq6Fa90hGKyDOvnpqOfkhv9ch
Itp5N78+Nmh1hrfNrSpoLYMruJdJrh8O58wSrtM+5NkoHJgdpPPvCXfdM0JEKZEw
xUlYk84YxBV3T4H4Tl6HJ8umIu+mX38a1azXM9rkJ3+8W4FuH/3+7lC97OKlztzI
u+S1wu2N0etP7KhxjccLMtqobnvyodoNhfy6EidrLdCZz9DYPADjPtp75mjNd5w8
RHCufuHFheoKRfovazjbApIlwnOh7Q==
=/pOe
-----END PGP SIGNATURE-----



More information about the Pkg-gtkpod-devel mailing list