Re: gnupg-2.2.4: how to deal with failed tests

2018-01-20 Thread MFPA
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On Friday 19 January 2018 at 3:50:22 PM, in , Shannon Mess via Gnupg-users wrote:- > REMOVE my email address from this thread! You are subscribed to the mailing list or not subscribed to it.

Re: gnupg-2.2.4: how to deal with failed tests

2018-01-19 Thread Shannon Mess via Gnupg-users
REMOVE my email address from this thread!  On Friday, January 19, 2018, 8:27:25 AM EST, Henry wrote: THANK YOU!! THANK YOU!! Configured simply with: % ./configure --enable-g13 --enable-symcryptrun --enable-wks-tools \   --with-readline=/usr/local and all tests run

Re: gnupg-2.2.4: how to deal with failed tests

2018-01-19 Thread Henry
THANK YOU!! THANK YOU!! Configured simply with: % ./configure --enable-g13 --enable-symcryptrun --enable-wks-tools \ --with-readline=/usr/local and all tests run seemed to PASS. (I will later be installing gnupg2 on darwin and ubuntu.) Henry 2018-01-19 3:27 GMT+09:00 Werner Koch

Re: gnupg-2.2.4: how to deal with failed tests

2018-01-18 Thread Werner Koch
On Thu, 18 Jan 2018 15:41, nbsd4e...@gmail.com said: > --enable-selinux-support --with-libgpg-error-prefix=/usr/local \ ^^ Ah! There is a second case where you see the reported error message: #ifdef ENABLE_SELINUX_HACKS if (1) { /* We don't allow

Re: gnupg-2.2.4: how to deal with failed tests

2018-01-18 Thread Henry
2018-01-18 4:12 GMT+09:00 Werner Koch : > On Wed, 17 Jan 2018 15:18, nbsd4e...@gmail.com said: > >> "gpg: importing secret keys not allowed" > > Which means you are trying to import from a keyserver, WKD, DANE etc. I do not know; the tests are trying to do it, AFAIK. > That is

Re: gnupg-2.2.4: how to deal with failed tests

2018-01-17 Thread Werner Koch
On Wed, 17 Jan 2018 15:18, nbsd4e...@gmail.com said: > "gpg: importing secret keys not allowed" Which means you are trying to import from a keyserver, WKD, DANE etc. That is very strange. How did you build gnupg, did you checked the signature of the source, is there anything special in your

Re: gnupg-2.2.4: how to deal with failed tests

2018-01-17 Thread Henry
Thank you very much. The log files seem to indicate there is some problem involving import of "secret keys". Still, I have no idea how to solve this problem. Excerpts from those files below. -- Henry issue2346.scm.log, ssh-export.scm.log,and ecc.scm.log all have in common the following: "gpg:

Re: gnupg-2.2.4: how to deal with failed tests

2018-01-17 Thread Kristian Fiskerstrand
On 01/17/2018 07:50 AM, Henry wrote: > I finally got gnugp2 built without any fatal errors. > Most of the tests passed, but the following tests failed: > tests/openpgp/issue2346.scm > tests/openpgp/ssh-export.scm > tests/openpgp/export.scm > tests/openpgp/ecc.scm > tests/openpgp/armor.scm > > I

Re: gnupg-2.2.4: how to deal with failed tests

2018-01-17 Thread Werner Koch
On Wed, 17 Jan 2018 07:50, nbsd4e...@gmail.com said: > tests/openpgp/armor.scm There will be a file tests/openpgp/armor.scm.log which should give you some more insight. You can alos run single tests or all in a more verbose mode. See the ERADME file in the tests directory. > Grateful for

gnupg-2.2.4: how to deal with failed tests

2018-01-16 Thread Henry
I finally got gnugp2 built without any fatal errors. Most of the tests passed, but the following tests failed: tests/openpgp/issue2346.scm tests/openpgp/ssh-export.scm tests/openpgp/export.scm tests/openpgp/ecc.scm tests/openpgp/armor.scm I am not hip on using a binary that fails its tests.