On Sat, Mar 22, 2008 at 10:22:18PM +0100, Christoph Berg wrote:
> Re: Paul Wise 2008-03-04 <1204622912.32309.9.ca...@chianamo>
> > * bad other sig: big, option to force unpack
> > * no sig: yay, unpack, warn about no sig
>
> I think the keyring selection should be done via the dscverif
Re: Paul Wise 2008-03-04 <[EMAIL PROTECTED]>
> * bad other sig: big, option to force unpack
> * no sig: yay, unpack, warn about no sig
I think the keyring selection should be done via the dscverify config.
What we probably should support is a mode where unsigned packages are
unpacked,
On Tue, 2008-03-04 at 07:44 +, Adam D. Barratt wrote:
> Is this an option that you'd only want to use when dget is calling
> dscverify, or any time that dscverify is called? If the latter then the
> functionality already exists (DSCVERIFY_KEYRINGS).
My use-case is downloading packages from me
On Tue, 2008-03-04 at 15:53 +0900, Paul Wise wrote:
> I would like an option I can put in my ~/.devscripts and use on the
> command line to make dget verify signatures using my regular gpg keyring
> as well as the debian-keyring.
Is this an option that you'd only want to use when dget is calling
d
Package: devscripts
Version: 2.10.18.1
Severity: wishlist
I would like an option I can put in my ~/.devscripts and use on the
command line to make dget verify signatures using my regular gpg keyring
as well as the debian-keyring. Alternatively change dscverify to check
~/.gnupg/pubring.gpg but pri
5 matches
Mail list logo
