[pkg-go] golang-codegangsta-cli and upstream branch

Vincent Bernat bernat at debian.org
Thu Jul 14 09:40:54 UTC 2016


 ❦ 14 juillet 2016 09:47 CEST, Dmitry Smirnov <onlyjob at debian.org> :

>> I am using "gbp import-orig" (with --uscan if possible),
>
> Me too. :)
>
>
>> so I don't see
>> this branch as particularly difficult to maintain.
>
> Not too difficult. But quite often it fails on merge to "master"... Also 
> repacking orig tarball and re-importing it with "gbp import-orig" have little 
> value, given the effort. Imported tarballs quickly depreciate and maintenance 
> cost is not negligible. KDE team maintains all their packages without 
> overhead of "upstream" branches. IMHO abandoning "upstream" branches 
> (especially if they are used merely to accommodate imported tarballs) would 
> be particularly beneficial to our team where so many packages need DFSG-
> cleanup and repackaging.

Note that uscan can do the repack automatically (with excluded files
listed from debian/copyright). However, it only works if there is a
tarball to download (so with git snapshots, this may be difficult, but
maybe there is a creative way to do that).

As for the matter, I have no strong opinion on this. Having the same
convention for all packages would be nice, of course.
-- 
Many pages make a thick book, except for pocket Bibles which are on very
very thin paper.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 818 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-go-maintainers/attachments/20160714/90cbd3b6/attachment-0001.sig>


More information about the Pkg-go-maintainers mailing list