From: brdelphus <brdelphus@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] lxc-4.0.4_1 with both gnupg 1.x and 2.x
Date: Tue, 20 Oct 2020 15:40:26 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-25750@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1058 bytes --]
New issue by brdelphus on void-packages repository
https://github.com/void-linux/void-packages/issues/25750
Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System
* xuname:
Void 5.8.16_1 x86_64 GenuineIntel uptodate rFFF
* package:
*affected package(s) including the version*: lxc-4.0.4_1
### Expected behavior
the ability to use download template to download os container templates
### Actual behavior
ERROR: Unable to fetch GPG key from keyserver
### Steps to reproduce the behavior
lxc-create -n mycontainer -t download -- --dist voidlinux --release current --arch x86_64
Further investigation shows me that the gpg option --receive-keys was -recv-keys on gnupg 1.x
reason why it fails to store necessary keys, not sending pull requests cos I am not familiar with
(we either specify which version of gnupg to be used, or check gpg simlinks to match template)
Thank you
next reply other threads:[~2020-10-20 13:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-20 13:40 brdelphus [this message]
2020-10-20 13:46 ` brdelphus
2020-10-20 13:49 ` brdelphus
2020-10-28 20:07 ` CameronNemo
2021-01-21 17:42 ` ericonr
2021-08-11 22:41 ` paper42
2021-08-11 22:41 ` [ISSUE] [CLOSED] " paper42
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-25750@inbox.vuxu.org \
--to=brdelphus@users.noreply.github.com \
--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).