Description of problem: Run any gpg2 command, and you get a warning as follows: NOTE: THIS IS A DEVELOPMENT VERSION! It is only intended for test purposes and should NOT be used in a production environment or with production keys! This doesn't put confidence in the security of the distribution (e.g. if the first thing I do after installation is verify the signatures of the hashes of the ISOs I just installed from). Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Install 2. Log in 3. Start terminal emulator 4. Run gpg2 --version (or any other gpg2 command) See https://dev.gnupg.org/rG39e551985d74d6ee9a87bde1c32ecdd1433c00cf for when this was introduced. We are triggering it by running ./autogen.sh in a non-git checkout which is resulting in the configure script using a version string indicating it is a beta release. We should either: - Not run ./autogen.sh if not necessary - Patch autogen.sh to indicate it was stable and use the RPM release as the additional version information. Patch coming ....
With this patch: --- gnupg-2.1.21/autogen.sh.orig 2017-03-17 10:34:37.000000000 +0200 +++ gnupg-2.1.21/autogen.sh 2017-06-06 21:24:21.624726814 +0200 @@ -245,8 +245,8 @@ if [ "$myhost" = "find-version" ]; then rvd=$((0x$(echo ${rev} | dd bs=1 count=4 2>/dev/null))) else ingit=no - beta=yes - tmp="-unknown" + beta=no + tmp="-${RPM_PACKAGE_RELEASE:-unknown}" rev="0000000" rvd="0" fi Building the package with running autogen.sh gives: [root@localhost ~]# gpg2 --version gpg (GnuPG) 2.1.21-1.mga6 libgcrypt 1.7.6 Copyright (C) 2017 Free Software Foundation, Inc. .... Building the package without running autogen.sh gives: [root@localhost ~]# gpg2 --version gpg (GnuPG) 2.1.21 libgcrypt 1.7.6 Copyright (C) 2017 Free Software Foundation, Inc.
Assigning to all packagers collectively, since there is no registered maintainer for this package.
Priority: Normal => release_blockerCC: (none) => marja11Assignee: bugsquad => pkg-bugs
It looks like a fix was committed but we haven't pushed it? Is there a reason for this?
CC: (none) => ngompa13
The pkg was submitted but failed on the buildsystem in %check Makefile:928: recipe for target 'xcheck' failed make[2]: *** [xcheck] Error 28 make[2]: Leaving directory '/home/iurt/rpmbuild/BUILD/gnupg-2.1.21/tests/openpgp' Makefile:533: recipe for target 'check-recursive' failed make[1]: *** [check-recursive] Error 1 make[1]: Leaving directory '/home/iurt/rpmbuild/BUILD/gnupg-2.1.21/tests' Makefile:588: recipe for target 'check-recursive' failed make: *** [check-recursive] Error 1 error: Bad exit status from /home/iurt/rpmbuild/tmp/rpm-tmp.lFgYcu (%check) It did pass all test when Buchan built it locally and also built for me locally.
CC: (none) => cae
The package fails to build in the buildsystem occasionally (Pascal posited that it might have to do with entropy requirements). Usually resubmitting fixes it. :/
For the entropy problems I ended up running rngd on arm build nodes (which had 100% failure) # Else some tests fail due to lack of entropy rpm -q rng-utils || urpmi rng-utils rngd -r /dev/urandom Here the package fails with that error even on arm so it's unlikely to be the problem.
CC: (none) => pterjan
I just tried building locally in iurt and get the same failure
Disabling the patch, I get 100% success in iurt, enabling the patch I get 100% failure but no idea why. The way to start a gpg-agent in %check is probably broken ++ ./agent/gpg-agent --use-standard-socket --daemon --write-env-file gpg-agent-info gpg-agent[4488]: WARNING: "--use-standard-socket" is an obsolete option - it has no effect gpg-agent[4488]: WARNING: "--write-env-file" is an obsolete option - it has no effect gpg-agent[4488]: directory '/home/pterjan/.gnupg' created gpg-agent[4488]: directory '/home/pterjan/.gnupg/private-keys-v1.d' created gpg-agent[4489]: gpg-agent (GnuPG) 2.1.21-2.mga6 started + eval modern way would probably be /agent/gpg-agent || ./agent/gpg-agent --daemon
I just committed a patch from Fedora that fixes the build for me locally with mock and all the tests passing.
This is now fixed with gnupg2-2.1.21-2.mga6.
Resolution: (none) => FIXEDStatus: NEW => RESOLVED