Bug#873499: Should depend on "gnupg | gnupg2 | gpg"

Control: affects 873499 src:gnupg2 On Mon 2017-08-28 14:36:20 +0200, Yuri D'Elia wrote: > The gnupg2 package in unstable has been renamed again and split into several > components. > > The "gnupg" package is now the full suite, while "gpg" contains the binary > itself. To avoid extra

Bug#873499: GnuPG package split and interlocking dependencies [was: Re: Bug#873499: Should depend on "gnupg | gnupg2 | gpg"]

On Mon, Sep 11 2017, Daniel Kahn Gillmor wrote: >> I'd recommend gpg-agent, and suggest gnupg instead. > > why? upstream recommends shipping all the binaries in a single package > as the standard deployment. I'm trying to meet them halfway here. <...> > I'm willing to keep the split in debian to

Bug#873499: GnuPG package split and interlocking dependencies [was: Re: Bug#873499: Should depend on "gnupg | gnupg2 | gpg"]

[ moving (and setting m-f-t) to pkg-gnupg-maint, which is a more appropriate forum for this discussion. for folks just joining us for the backlog, please see https://bugs.debian.org/873499 ] On Mon 2017-09-11 16:56:39 +0200, Yuri D'Elia wrote: > On Mon, Sep 11 2017, Daniel Kahn Gillmor

Bug#873499: Should depend on "gnupg | gnupg2 | gpg"

On Mon, Sep 11 2017, Daniel Kahn Gillmor wrote: > On Mon 2017-09-11 14:28:29 +0200, Yuri D'Elia wrote: >> I'd rather go for this route, and recommend gpg-agent from gpg, > > gpg already Recommends: gnupg, which itself Depends: gpg-agent. I'd recommend gpg-agent, and suggest gnupg instead. >

Bug#873499: Should depend on "gnupg | gnupg2 | gpg"

On Mon 2017-09-11 14:28:29 +0200, Yuri D'Elia wrote: > I'd rather go for this route, and recommend gpg-agent from gpg, gpg already Recommends: gnupg, which itself Depends: gpg-agent. > mentioning that secret key operations require at least the agent to be > running in the description. Please

Bug#873499: Should depend on "gnupg | gnupg2 | gpg"

On Mon, Sep 11 2017, Daniel Kahn Gillmor wrote: > gpg: failed to start agent '/usr/bin/gpg-agent': No such file or directory > gpg: can't connect to the agent: No such file or directory > gpg: agent_genkey failed: No agent running > Key generation failed: No agent running > 2 dkg@sid:~$ Since I

Bug#873499: Should depend on "gnupg | gnupg2 | gpg"

On Tue 2017-08-29 11:04:01 +0200, Yuri D'Elia wrote: > On Tue, Aug 29 2017, Colin Watson wrote: >> This package contains /usr/bin/gpg itself, and is useful on its own >> only for public key operations (encryption, signature verification, >> listing OpenPGP certificates, etc). If you want full

Bug#873499: Should depend on "gnupg | gnupg2 | gpg"

On Tue, 29 Aug 2017 06:05:06 +0100 Colin Watson wrote: > On Mon, Aug 28, 2017 at 02:36:20PM +0200, Yuri D'Elia wrote: > > The gnupg2 package in unstable has been renamed again and split into several > > components. > > > > The "gnupg" package is now the full suite, while

Bug#873499: Should depend on "gnupg | gnupg2 | gpg"

On Tue, Aug 29 2017, Colin Watson wrote: > This package contains /usr/bin/gpg itself, and is useful on its own > only for public key operations (encryption, signature verification, > listing OpenPGP certificates, etc). If you want full capabilities > (including secret key operations, network

Bug#873499: Should depend on "gnupg | gnupg2 | gpg"

On Mon, Aug 28, 2017 at 02:36:20PM +0200, Yuri D'Elia wrote: > The gnupg2 package in unstable has been renamed again and split into several > components. > > The "gnupg" package is now the full suite, while "gpg" contains the binary > itself. To avoid extra dependencies, it would be nice to

Bug#873499: Should depend on "gnupg | gnupg2 | gpg"

Package: pass Version: 1.7.1-3 Severity: normal The gnupg2 package in unstable has been renamed again and split into several components. The "gnupg" package is now the full suite, while "gpg" contains the binary itself. To avoid extra dependencies, it would be nice to update the dependency to