Hi Otto, On Thu, 2024-12-05 at 21:58 -0800, Otto Kekäläinen wrote: > 1. Switch to most recent and final DEP14 names 'debian/latest' and > 'upstream/latest': https://github.com/Debian/dh-make-golang/pull/225 > > Go team already follows DEP14 since 2019, but the standard evolved, so > Go team should update accordingly. We can start doing this in new > packages by merging the PR above, and then later update old packages > by using upcoming dep14-convert script from devscripts. > > 2. Use name 'upstreamvcs' for upstream instead of 'upstream' > > See https://salsa.debian.org/go-team/infra/pkg-go-tools/-/merge_requests/3. > This makes use of DEP14 easier, and makes Go team guidance also > compatible with `gbp clone vcs-git:<package> --add-upstream-vcs` > command.
Does this mean that maintaining upstream Git history will be standard in the Go team? Personally, I prefer the simpler method of not pulling from upstream and just importing from a tarball, as it results in better (IMO) commit history[1] and it is much easier to revert or checkout previous upstream versions (i.e. simpler navigation of packaging commit history). In addition, pulling from upstream introduces tagging problems and results in either: 1. Two identical tags from upstream (e.g. "v2.2.4") and gbp (e.g. "upstream/2.2.4") being created. 2. The "upstream/2.2.4" tag format not being used at all. (I have seen both of these occur when upstream history is incorporated.) -- Maytham Alsudany Debian Maintainer maytham @ OFTC maytha8 @ Libera [1]: e.g. https://salsa.debian.org/go-team/packages/miniflux/-/commits/upstream/ It will also avoid drowning out previous packaging commits with upstream commits, e.g. https://salsa.debian.org/go-team/packages/miniflux/-/commits/debian/sid/ compared to https://salsa.debian.org/go-team/packages/gh/-/commits/debian/sid/
signature.asc
Description: This is a digitally signed message part
