Github messages for voidlinux
 help / color / mirror / Atom feed
From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: kgpg: fix
Date: Fri, 27 Sep 2019 17:26:02 +0200	[thread overview]
Message-ID: <20190927152602.2jc9G8AhtnYvYLTC9F0Lkg3W5NSEtXaMhHctZeulMiQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-14741@inbox.vuxu.org>

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

New comment by k4leg on void-packages repository

https://github.com/void-linux/void-packages/pull/14741#issuecomment-535632150

Comment:
Hmm, strange... I don’t have a choice of algorithms when trying to create keys, and if I try to create them, it will either give an error or create the illusion that it is being created, but actually does nothing.
In addition, if I’m not mistaken, as you said, it sets gpgme as a transistor dependence, and gpgme, in turn, depends on gnupg2, so, as for me, it’s better not to add this dependence (gnupg), but fix it in compilation time. As I said, for example, for some reason, he does not apply the actions that I told him during the first run (use /usr/bin/gpg2, and not /usr/bin/gpg) (maybe this is due to that by default it shows the correct path to gpg2 and believes that it has already set the place gpg -> gpg2).

  parent reply	other threads:[~2019-09-27 15:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-26 16:07 [PR PATCH] " voidlinux-github
2019-09-26 16:09 ` [PR PATCH] [Updated] " voidlinux-github
2019-09-26 16:09 ` voidlinux-github
2019-09-26 16:29 ` voidlinux-github
2019-09-26 16:29 ` voidlinux-github
2019-09-26 18:03 ` voidlinux-github
2019-09-26 18:35 ` voidlinux-github
2019-09-27 15:14 ` voidlinux-github
2019-09-27 15:15 ` voidlinux-github
2019-09-27 15:26 ` voidlinux-github [this message]
2019-09-30 18:21 ` voidlinux-github
2019-10-02 14:13 ` voidlinux-github

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=20190927152602.2jc9G8AhtnYvYLTC9F0Lkg3W5NSEtXaMhHctZeulMiQ@z \
    --to=voidlinux-github@inbox.vuxu.org \
    --cc=ml@inbox.vuxu.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. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).