I just use dh-make-golang to produce new upstream tarballs. See also https://github.com/Debian/dh-make-golang/issues/14
On Wed, Sep 2, 2015 at 4:46 AM, Dmitry Smirnov <only...@debian.org> wrote: > On Wednesday 02 September 2015 12:52:56 Martín Ferrari wrote: >> There is a very well documented and tidy process for doing all this, >> although it is probably way too complicated for most people. Still, it >> is a good read to have an idea of how to do things: >> http://blog.mycre.ws/articles/git-packaging-workflow-for-py-lmdb/ > > Thank you for detailed replay and for all your hints. Indeed I find it too > complicated. :( I merely cloned one of our packages' repository and managed > to produce a release tarball from HEAD of upstream repository by using "dh- > make-golang" which is a bit awkward yet a lot simpler than to configure git > remote and fetch history of all upstream changes since beginning of time > merely to generate tarball for "gbp import-orig"... > > >> Another read: DEP-14, which documents some best-practices for debian/git >> packaging: http://dep.debian.net/deps/dep14/ > > IMHO this is too GBP-oriented approach. My favourite layout of debian package > repositories is documented here: > > https://pkg-kde.alioth.debian.org/gitguidelines.html > > Unfortunately it does not answer the question how to easily produce orig.tar > from tagless GitHub repositories... > > -- > Regards, > Dmitry Smirnov. > > --- > > Good luck happens when preparedness meets opportunity. > > _______________________________________________ > Pkg-go-maintainers mailing list > Pkg-go-maintainers@lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers -- Best regards, Michael _______________________________________________ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers