Hi Guido, The pkg-go team is currently discussing changes to its workflow, and we’d be interested in resolving this feature request.
Guido Günther <a...@sigxcpu.org> writes: > I would rather do this with a dfsg-clean branch. You delete once and > then use git tools from there on. Searching for how dfsg-clean branches should be named, I found https://honk.sigxcpu.org/projects/git-buildpackage/manual-html/gbp.branch.naming.html, which recommends “dfsg/latest”. However, my reading of section “About repacked upstream sources” of http://dep.debian.net/deps/dep14/ directly contradicts the above advice: DEP14 says upstream/* should contain the repackaged files. How do we reconcile this apparent contradiction? >> It would be great if gbp could produce the 1.2.3+dfsg tag itself by >> reading debian/copyright and excluding the Files-Excluded: files. > > If somebody comes up with a clean patch I'm happy to merge that. Which part of gbp specifically should be patched here? AFAICT, there is no command which pulls a new version from upstream yet. Should one be added? What should it be called? -- Best regards, Michael
