control: clone -1 -2 control: retitle -2 pristine-tar should sign git commits if enabled in git
Hi Mattia, There are several issues here so let's split them: On Tue, Jan 02, 2018 at 12:12:15AM +0100, Mattia Rizzolo wrote: > Package: git-buildpackage > Version: 0.9.5 > > Since some time (long time actually, but I never got around to report > it, probably even a whole year) `gbp import-orig` is not signing the > commits in the upstream and pristine-tar branches, despite me having > commit.pgpsign = true > in my ~/.gitconfig. [..snip..] > I'm very sure it used to sign everything in the past, so I don't really > understand why it stopped, but even if it wasn't a regression I'd still > call it a bug that it's overriding my git config :) Try pristine-tar without using gpg and it will not sign your commit so this should _also_ be filed against pristine-tar (so cloning this report) Cheers, -- Guido
