On Mar 7, 2020, at 7:58 AM, Tong Sun <suntong...@gmail.com> wrote: > > On Fri, Mar 6, 2020 at 11:35 PM Anthony Fok <f...@debian.org> wrote: >> >> On Fri, Mar 6, 2020 at 7:12 PM Tong Sun <suntong...@gmail.com> wrote: >>> . . . >>> - My dh-make-golang is v0.3.3 linux/amd64, updated just days ago. >>> - Whether I don't provide the -pristine-tar flag, or use >>> `-pristine-tar=false` I always get the pristine-tar branch: >>> . . . >>> >>> How were you able to only get two branches? >> >> Check and see if you have "pristine-tar = True" defined in ~/.gbp.conf >> or /etc/git-buildpackage/gbp.conf . >> If so, remove that line. > > Aha! Thank a lot Anthony!
One small point about not using pristine-tar: today I tried to upload backports of a number of packages packaged with the new workflow. All of the uploads got rejected because of a mismatched tarball. The fix was pretty easy - just grab the orig from the archives and rebuild, but it was definitely an added hassle that wasn’t a problem when using pristine-tar. Not really complaining, just wanted to add another datapoint. :) Stephen
