Bug#963968: git-buildpackage: import-orig fails to find component tarball signatures

2020-07-01 Thread Guido Günther
Hi, On Wed, Jul 01, 2020 at 09:46:41PM +1000, Hugh McMaster wrote: > Hi Guido, > > On Tue, 30 Jun 2020 at 18:22, Guido Günther wrote: > > There's two issues: > > > > - gbp did not properly check for the existence of component signatures, > > that is fixed on master: > > Yes, I pulled your

Bug#963968: git-buildpackage: import-orig fails to find component tarball signatures

2020-06-30 Thread Guido Günther
Hi, On Mon, Jun 29, 2020 at 11:17:51PM +1000, Hugh McMaster wrote: > On Mon, 29 Jun 2020 at 22:47, Guido Günther wrote: > > ahh...i see you're using component tarballs - that's likely the problem. > > Could you add > > > > > >

Bug#963968: git-buildpackage: import-orig fails to find component tarball signatures

2020-06-29 Thread Guido Günther
Hi, On Mon, Jun 29, 2020 at 10:14:04PM +1000, Hugh McMaster wrote: > Hi Guido, > > On Mon, 29 Jun 2020 at 22:00, Guido Günther wrote: > > this looks as if `import-orig` looks on your pristine-tar branch and > > does not find a signature there (but already finds a pristine-tar > > commit) > >

Bug#963968: git-buildpackage: import-orig fails to find component tarball signatures

2020-06-29 Thread Guido Günther
Hi, On Mon, Jun 29, 2020 at 09:53:54PM +1000, Hugh McMaster wrote: [..snip..] > gbp:debug: ['git', 'rev-parse', '--quiet', '--verify', 'pristine-tar'] > gbp:error: ../freetype_2.10.2.orig-ft2docs.tar.xz does not have a signature > file this looks as if `import-orig` looks on your pristine-tar