gpg: handle ASCII-armored keyrings as well #1

gpg command "--list-keys" requires input files to be passed with
option "--keyring" and each file must match type "public keyring v4"
while gpg command "--show-keys" doesn't require extra options and
handles also ASCII-armored public keyrings as well.

Signed-off-by: Konstantin Demin rockdrilla@gmail.com

gpg command "--list-keys" requires input files to be passed with option "--keyring" and each file must match type "public keyring v4" while gpg command "--show-keys" doesn't require extra options and handles also ASCII-armored public keyrings as well. Signed-off-by: Konstantin Demin <rockdrilla@gmail.com>

Hi, you are the first to use my new self hosted code hosting platform using gitea instead of gitlab (which was a pain to maintain). I hope that nothing breaks as I'm still in the early stages of trying out this platform. Apparently stuff like user registration, pull requests and email notifiations seem to work just fine! :D

I'm also happy that you are persistent with getting your improvements merged. Unfortunately your changes break the test suite. Did you run the tests?

Hi, you are the first to use my new self hosted code hosting platform using gitea instead of gitlab (which was a pain to maintain). I hope that nothing breaks as I'm still in the early stages of trying out this platform. Apparently stuff like user registration, pull requests and email notifiations seem to work just fine! :D I'm also happy that you are persistent with getting your improvements merged. Unfortunately your changes break the test suite. Did you run the tests?

Hi, you are the first to use my new self hosted code hosting platform using gitea instead of gitlab (which was a pain to maintain). I hope that nothing breaks as I'm still in the early stages of trying out this platform. Apparently stuff like user registration, pull requests and email notifiations seem to work just fine! :D

I'm happy too! xD

I'm also happy that you are persistent with getting your improvements merged. Unfortunately your changes break the test suite. Did you run the tests?

Test suite was broken some time ago, but I've fixed that issue (I hope so): I've added some checks against empty files which was pain for gnupg and also I've muted gnupg warning about "trustness" just initializing empty trustdb.

Nevertheless, I'm going to put script to run all night long to test that everything is ok.

> Hi, you are the first to use my new self hosted code hosting platform using gitea instead of gitlab (which was a pain to maintain). I hope that nothing breaks as I'm still in the early stages of trying out this platform. Apparently stuff like user registration, pull requests and email notifiations seem to work just fine! :D I'm happy too! xD > I'm also happy that you are persistent with getting your improvements merged. Unfortunately your changes break the test suite. Did you run the tests? Test suite was broken some time ago, but I've fixed that issue (I hope so): I've added some checks against empty files which was pain for gnupg and also I've muted gnupg warning about "trustness" just initializing empty trustdb. Nevertheless, I'm going to put script to run all night long to test that everything is ok.

Tests are failing on other point: (169/193) mode=proot,variant=debootstrap: create tarball.
Command: ./make_mirror.sh ; ONLINE=yes CMD=./mmdebstrap ./coverage.sh

I think this is due to heavy load with qemu/kvm.
I also have "amdgpu" wailing in dmesg. 😂

Tests are failing on other point: (169/193) mode=proot,variant=debootstrap: create tarball. Command: ./make_mirror.sh ; ONLINE=yes CMD=./mmdebstrap ./coverage.sh I think this is due to heavy load with qemu/kvm. I also have "amdgpu" wailing in dmesg. 😂

Try running:

./make_mirror.sh
HAVE_PROOT=no CMD=./mmdebstrap ./coverage.sh

proot support is kinda borked these days...

Try running: ./make_mirror.sh HAVE_PROOT=no CMD=./mmdebstrap ./coverage.sh proot support is kinda borked these days...

Test suite required a lot of resources, so I can't launch it on my vps for all night long. I also can't launch it on my laptop because it loads my system hard.

Did you change something compared to your last pull request? The test suite passes successfully now. I can merge it now.

Did you change something compared to your last pull request? The test suite passes successfully now.

Of course. :)

> Did you change something compared to your last pull request? The test suite passes successfully now. Of course. :)

fixed by ccd4b5c163

fixed by ccd4b5c163d322045c92f734f43bb5e1945fa774

Labels Milestones

gpg: handle ASCII-armored keyrings as well #1

Step 1:

Step 2: