On Thu, Jul 7, 2022 at 12:04 AM Domenico Andreoli <ca...@debian.org> wrote: > > On Fri, Jun 24, 2022 at 10:43:35PM +0800, Shengjing Zhu wrote: > > On Mon, Jun 13, 2022 at 5:11 AM Domenico Andreoli <ca...@debian.org> wrote: > > > > > > Dear DGPT, > > > > > > I see that dh-make-golang creates the `upstream` branch and an empty > > > commit "New upstream version..." on it, eg. [0]. > > > > > > What's the purpose of such empty commit? I can't find anything related > > > in DEP-14 [1]. > > > > > > I would expect that the upstream branch tracked the upstream repo > > > without any change. > > > > dh-make-golang just calls git-buildpackage[1], which is > > > > gbp import-orig ../<source>_<ver>.tar.gz --upstream-vcs-tag=<ver> > > > > [1] > > https://github.com/Debian/dh-make-golang/blob/52983fc8eecb1ab488d7efa28d0298b65317060a/make.go#L511 > > Thanks! > > That makes totally sense for tarball-based releases indeed but do we > agree that the git-based releases of the Go world could play better? >
Sometime we can't keep upstream branch without any change. For example you need to repack, like removing vendor directory, which is very common previously (before go module). In that case `gbp import-orig` with `--upstream-vcs-tag` option works almost well. -- Shengjing Zhu
