Otto Kekäläinen <otto@debian.org> writes: > Hi, > > .. >> I'm not sure --upstream-vcs-tag=<commit-ish> can be set in >> debian/gbp.conf in any reasonable way though...? Setting >> 'upstream-tag=' doesn't achieve exactly the same, I think. > > You wrote this one day after I posted the recommended debian/gbp.conf > template in https://lists.debian.org/debian-go/2025/11/msg00006.html, > I wonder if you read that message? 'Read' does not always mean 'understood' or 'took action on' :) > You can simply copy the line `upstream-vcs-tag = v%(version%~%-)s` > from the template - it works without any modifications for your I added that here, and did an 'gbp import-orig' and things look different, is this correct? https://salsa.debian.org/jas/golang-golang-x-time/ I'm going to update that package too, and people think that repository looks better, I can fix the other x-* packages too. Is this documented anywhere? This seems like a rather subjective and possibly opinionated configuration, and I'm wondering if the fact it is not part of debian/gbp.conf is that only some people prefer this way. Is there concensus on changing Go Team policy on this? I really don't care except for consistency on this. I think we are likely to keep repeating the same mistake (and discussion) otherwise. > For a visual explanation of all the git-buildpackage branches and tags > see https://optimizedbyotto.com/post/debian-source-package-git/ > > Reading > https://optimizedbyotto.com/post/debian-packaging-from-git/#import-new-upstream-versions-in-the-future > might also be of interest. Thank you for publishing those! /Simon
Attachment:
signature.asc
Description: PGP signature