all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Jesse Gibbons <jgibbons2357@gmail.com>
To: Leo Prikler <leo.prikler@student.tugraz.at>, 38491@debbugs.gnu.org
Subject: bug#38491: Evolution is missing GPG
Date: Thu, 05 Dec 2019 09:53:50 -0700	[thread overview]
Message-ID: <36bd0ad85c26bdee2d5a957b1f067fa24f67f3e1.camel@gmail.com> (raw)
In-Reply-To: <51e3a6f2bca86b7ad6107ec921c54464f4f6a51e.camel@student.tugraz.at>

On Wed, 2019-12-04 at 13:11 +0100, Leo Prikler wrote:
> Hi Guix,
> 
> I recently discovered, that Evolution would complain about a missing
> GPG whenever it encounters a signed message.  For the record, I've only
> installed evolution-data-server in the operating-system and evolution
> itself inside my user profile and not installed gpg in either place,
> thus causing this issue.  Would it make sense to make gpg an input to
> evolution and hardcode the path in the source?  Or would it perhaps be
> better to have it as propagated input?  WDYT?
> 
> Regards,
> Leo
> 
> 
> 
> 
Guix complains that it cannot find gpg when I call "guix import gnu
<package>". But unless I'm using a function of guix that depends on gpg,
guix is not broken, so gpg is not an input or propagated input of guix. I
think we have the same situation here. Evolution is functional without GPG,
and handles itself fairly well when gpg is not found.

Try installing gpg locally and see if it stops complaining. If so, we have a
solution. If not, we should consider adding GPG as a propagated input to
Evolution.

  reply	other threads:[~2019-12-05 16:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-04 12:11 bug#38491: Evolution is missing GPG Leo Prikler
2019-12-05 16:53 ` Jesse Gibbons [this message]
2019-12-05 17:51   ` Leo Prikler
2019-12-07 16:45     ` Jesse Gibbons

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=36bd0ad85c26bdee2d5a957b1f067fa24f67f3e1.camel@gmail.com \
    --to=jgibbons2357@gmail.com \
    --cc=38491@debbugs.gnu.org \
    --cc=leo.prikler@student.tugraz.at \
    /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.