Re: Bug#1111127: ITP: golang-go.yaml-yaml-v3 -- YAML Support for the Go Language
Hi,
> In future, please try to preserve the upstream git commit history. I know that some people are still in the pristine-tar mindset, which squashes (stomps?) upstream git history down to a single merge commit. However, it's a lot easier to track down the origin and date of bugs when the Debian repo history matches the upstream history.
>
> Incidentally, this is the very first point in the Debian Go Team workflow, described at https://go-team.pages.debian.net/workflow-changes.html#wf-2017-11-upstream-branch (and the next point is phasing out pristine-tar branches).
I think we should have *both* upstream git history and pristine-tar to
ensure the tarball has the same shasum no matter who produces it. It
happens automatically if you have these lines in gbp.conf:
pristine-tar = True
upstream-vcs-tag = v%(version%~%-)s
See https://salsa.debian.org/go-team/packages/glow/-/blob/debian/latest/debian/gbp.conf
as an example
You can also see this in action if you want to browse the branches and
see how they merged etc:
gbp clone git@salsa.debian.org:go-team/packages/glow.git
gitk --all &
I've tried to explain some of the rationale in
https://optimizedbyotto.com/post/debian-source-package-git/
Reply to: