On 12/01/17 18:29, Barry Warsaw wrote: > Did the debdiff get deleted? I've landed here because gpgme1.0 ftbfs is > blocking claws-mail 3.14.1-2 promotion. I'm stuck (local build) on the > Qt-related build crash. If I can fix that, I'll investigate the Python > test suite hang. >
There is a diff here that was the original solution to getting configure to find Qt, and then continue to the build and tests. http://paste.ubuntu.com/23788286/ That should result in a successful LOCAL build with no test suite hang. However, as said, the same build on the launchpad builders result(ed) in a hang at the point in the tests already discussed. I have just quickly uploaded a test example here: https://launchpad.net/~rikmills/+archive/ubuntu/gpgme-tests I will cancel the amd64 build when it hangs to make the buildlog available, but will leave the other architectures to time out and eventually be killed by the launchpad build system itself. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gpgme1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1647204 Title: 1.8.0-2 FTBFS in zesty 17.04 Status in gpgme1.0 package in Ubuntu: Confirmed Bug description: 1.8.0-2 synced from debian in Zesty Zapus 17.04 fails to build on all architectures from source with the error: checking whether a simple qt program can be built... no configure: error: *** *** Qt5 (Qt5Core) is required for Qt binding. *** The packages builds without this issue in debian unstable. A little experimentation shows that is a ubuntu sbuild/pbuilder and ppa, setting -pie in the hardening options allows the build to proceed with the Qt bindings building properly. Not being overly familiar with the hardening, I am unsure if dropping that feature set is relatively harmless, or massively undesirable and potentially harmful. However, in a ppa build, but NOT in my local sbuild/pbuilder chroot, the resulting build then hangs on the (python?) tests on starting or stopping gpg-agent, and the build is eventually killed due to inactivity after 150 mins as follows GNUPGHOME=/<<PKGBUILDDIR>>/lang/python/tests LC_ALL=C GPG_AGENT_INFO= top_srcdir=../../.. srcdir=. LD_LIBRARY_PATH="../../../src/.libs:" /usr/bin/python3 ./run-tests.py \ --interpreters="/usr/bin/python /usr/bin/python3" --srcdir=. \ initial.py t-wrapper.py t-callbacks.py t-data.py t-encrypt.py t-encrypt-sym.py t-encrypt-sign.py t-sign.py t-signers.py t-decrypt.py t-verify.py t-decrypt-verify.py t-sig-notation.py t-export.py t-import.py t-trustlist.py t-edit.py t-keylist.py t-wait.py t-encrypt-large.py t-file-name.py t-idiomatic.py t-protocol-assuan.py final.py starting gpg-agent Session terminated, terminating shell...make[1]: *** wait: No child processes. Stop. make[1]: *** Waiting for unfinished jobs.... make[1]: *** wait: No child processes. Stop. make[3]: *** wait: No child processes. Stop. make[3]: *** Waiting for unfinished jobs.... make[3]: *** wait: No child processes. Stop. ...terminated. make: *** wait: No child processes. Stop. make: *** Waiting for unfinished jobs.... make: *** wait: No child processes. Stop. Makefile:457: recipe for target 'check-recursive' failed make[2]: *** [check-recursive] Terminated Makefile:602: recipe for target 'xcheck' failed make[4]: *** [xcheck] Terminated Build killed with signal TERM after 150 minutes of inactivity I would note that this is the first gpgme version from gpg directly, with the Qt bindings built. These will be essential for future KDE applications and frameworks, as the gpgmepp previously built in KDE's own packages is being dropped. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/1647204/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp