Use gbp buildpackage, instead of raw dpkg-buildpackage. Like that for example: $ gbp buildpackage --git-builder=dpkg-buildpackage -us -uc -ui -i -b
Builder can be set in $HOME/.gbp.conf, so you don't have to always specify --git-builder option. niedz., 24 mar 2019 o 22:42 Tong Sun <[email protected]> napisał(a): > > On Sun, Mar 17, 2019 at 9:31 AM Tong Sun wrote: > > > > On Sun, Mar 10, 2019 at 9:02 AM Tong Sun wrote: > > > > > Anywhere I can read about how to update golang packages? > > > > > > All the docs that I read were on *creating* packages with > > > dh-make-golang, and haven't got to updating them yet. please help. > > > > Found it, at > > https://honk.sigxcpu.org/projects/git-buildpackage/manual-html/gbp.patches.newupstream.html > > I'm following it, but my build is still *named* as old. > What I've missed? > > Here is what I did: > > $ gbp import-orig --uscan > gbp:info: Launching uscan... > uscan warn: No files matched excluded pattern as the last matching > glob: Godeps/_workspace > gbp:info: Using uscan downloaded tarball ../easygen_4.0.0.orig.tar.gz > gbp:info: Importing '../easygen_4.0.0.orig.tar.gz' to branch 'upstream'... > gbp:info: Source package is easygen > gbp:info: Upstream version is 4.0.0 > gbp:info: Replacing upstream source on 'master' > gbp:info: Successfully imported version 4.0.0 of ../easygen_4.0.0.orig.tar.gz > > then, > > $ dpkg-buildpackage -us -uc -ui -i -b > dpkg-buildpackage: info: source package easygen > dpkg-buildpackage: info: source version 3.0.0+git20180723.75369c3-1 > dpkg-buildpackage: info: source distribution unstable > . . . > > I.e., although gbp has successfully imported version 4.0.0, > dpkg-buildpackage still thinks the source version is 3.0.0+git... > and it creates such version file as well: > > $ dpkg -c ../easygen_3.0.0+git20180723.75369c3-1_amd64.deb > drwxr-xr-x root/root 0 2019-03-17 20:48 ./ > drwxr-xr-x root/root 0 2019-03-17 20:48 ./usr/ > drwxr-xr-x root/root 0 2019-03-17 20:48 ./usr/bin/ > -rwxr-xr-x root/root 3077224 2019-03-17 20:48 ./usr/bin/easygen > . . . > > However, judging from the content being built, I can tell that > dpkg-buildpackage IS building my 4.0 content. > > What step(s) I've missed? Thx >
