This package failed to rebuild for FC4 Development around 2005-04-11 after an automated release bump. Architectures: ppc Build failure logs at: http://fedoraproject.org/extras/development/build-logs/
It built fine on PPC for me. Interestingly, when I bumped the release number and resubmitted it, it failed on x86_64 in the same place... make[2]: Entering directory `/usr/src/rpm/BUILD/gnupg-1.9.15/tests' asschk: read_assuan: received incomplete line on fd 8 FAIL: sm-sign+verify PASS: sm-verify ====================================== 1 of 2 tests failed Please report to gnupg-devel ======================================
FYI, 1.9.16 is out.
This is the reason for above error message: : sending `VERIFY' : expecting OK : : gpgsm: some signal caught ... exiting
Any objections that I upgrade to 1.9.16 and make the code try to print the signal name? (could be SIGSEGV)
Knock yourself out. You can use http;//apt.kde-redhat.org/apt/kde-redhat/all/SRPMS.stable/gnupg-1.9.16-1.src.rpm as a starting point.
Ack. URL that actually works: http://apt.kde-redhat.org/apt/kde-redhat/all/SRPMS.stable/gnupg2-1.9.16-1.src.rpm
* ppc build succeeded * i386 and x86_64 timed out in the build system with no log :(
> Build of gnupg2 on development succeeded. 1.9.16-2 made it, apparently. I suggest we leave the strsignal patch in there to benefit from its output in case we run into a build failure again.