all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ng0 <ng0@we.make.ritual.n0.is>
To: guix-devel@gnu.org
Subject: Re: Install gpg2 as gpg
Date: Tue, 14 Jun 2016 12:49:42 +0000	[thread overview]
Message-ID: <20160614124942.GD3999@khazad-dum> (raw)
In-Reply-To: <20160614075246.GA1570@solar>

[-- Attachment #1: Type: text/plain, Size: 2217 bytes --]

On 2016-06-14(09:52:46AM+0200), Andreas Enge wrote:
> Hello,
>
> On Mon, Jun 13, 2016 at 05:07:08PM -0400, Leo Famulari wrote:
> > On Mon, Jun 13, 2016 at 08:24:23PM +0000, ng0 wrote:
> > > What if we patched gpg-1 to not colide with gpg-2?
> > >
> > > For example, move gpg and gpgv and man pages of them
> > > for gpg-1 to something which has -1 in its name.
> > > On the other hand this would have to be consistent and be followed
> > > straigth to not colide again. I'm not sure if this
> > > approach will work out in the long run.
> >
> > Unless this is a configuration option supported by upstream GnuPG, I
> > don't want to do that. For the same reason, my patch does not affect
> > gnupg-2.0.

The -as-gnupg2 option got me for a moment, I forgot that this is gnupg-1.

>
> I agree with this argument - one of our principles is to mess as little
> as possible with upstream packages. In this case, since there is a special
> configuration option for gnupg-2, we may use it, but then we would have
> to pay the price that both gnupg-1 (or gnupg-2.0) and gnupg-2.1 could not
> be installed together any more. Maybe it would then be consistent to drop
> gnupg-2.0 from the distribution.

gnupg-2.0 and gnupg-2.1 are currently individual packages which can be
installed side by side in guix?

> Finally I managed to make gnupg-2.1 work together with mutt, but it was
> not completely straightforward... So we should document the change if we
> make it.

Yes, there have been some changes, but they are documented upstream.
When this is desired for Guix, I can see if I can recall what I did
in 2015 where it went from working to broken to almost working and
now completely functional with GnuPG2.1.x

I'd be curious if it just works when I can move to GuixSD again with
libgcrypt-1.7 merged.

> By the way, should we maybe make pinentry a propagated input of gnupg-2.1?
> If I understand correctly, gnupg-2.1 will not work without it (and mixing
> pinentry from Debian with gnupg-2.1 from Guix was one of the reasons for
> gnupg not working at first).
>
> Andreas
>
>

--
♥Ⓐ ng0
For non-prism friendly talk find me on
psyced.org / loupsycedyglgamf.onion

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  parent reply	other threads:[~2016-06-14 12:49 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-13 19:55 Install gpg2 as gpg Leo Famulari
2016-06-13 20:24 ` ng0
2016-06-13 21:07   ` Leo Famulari
2016-06-14  7:52     ` Andreas Enge
2016-06-14 12:07       ` Ludovic Courtès
2016-06-14 12:49       ` ng0 [this message]
2016-06-14 13:37         ` Leo Famulari
2016-06-13 21:42 ` Christopher Allan Webber
2016-06-14 12:09 ` Ludovic Courtès
2016-06-14 13:50   ` Leo Famulari
2016-06-15 12:53     ` Andreas Enge
2016-06-15 15:02       ` Leo Famulari
2016-06-15 15:54         ` Andreas Enge
2016-06-16 10:56         ` Ludovic Courtès
2016-06-18  1:07           ` Leo Famulari
2016-06-19 14:03             ` Ludovic Courtès
2016-07-24 20:56               ` Ludovic Courtès
2016-07-24 21:10                 ` Leo Famulari

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160614124942.GD3999@khazad-dum \
    --to=ng0@we.make.ritual.n0.is \
    --cc=guix-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.