Re: [Touch-packages] [Bug 1647204] Re: 1.8.0-2 FTBFS in zesty 17.04
On Thu 2017-02-23 16:57:12 -0500, Launchpad Bug Tracker wrote:
> * Add in libgpgme-dev a libgpgme-pthread.so pointing to libgpgme.so, this
> will fix the build failures of kf5-kdepim-apps-libs when built against
> this
> gpgme package.
As i wrote when asked on IRC, i think this is the wrong fix for this
problem.
if kf5-kdepim-apps-libs is being built correctly, it should be using
gpgme-config from libgpgme-dev itself to choose how to link, which
should know which .so to link against.
why should this additional symlink be necessary for the build of
kf5-kdepim-apps-libs?
maybe i'm misunderstanding something about the build of
kf5-kdepim-apps-libs. can you explain more?
--dkg
--
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:
Fix Released
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=/<>/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
Re: [Touch-packages] [Bug 1647204] Re: 1.8.0-2 FTBFS in zesty 17.04
On Thu 2017-01-12 17:10:07 -0500, Rik Mills wrote: > Adding some debug statements on other the builds showed that that hang > is occurring in > > lang / python / tests / t-callbacks.py > > specifically, when the c.op_genkey call is made in the section shown > below. a hang during key generation is often due to lack of entropy on the system. Can you ensure that the system isn't entropy-starved somehow? --dkg -- 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=/<>/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
Re: [Touch-packages] [Bug 1647204] Re: 1.8.0-2 FTBFS in zesty 17.04
On Fri 2016-12-30 20:19:04 -0500, Colin Watson wrote: > Sounds like the problem is that this build leaves processes hanging > around from its tests. Unfortunately this currently causes builds to > hang, basically because launchpad-buildd uses sbuild's sudo mode rather > than its schroot mode. So the hang is a known bug in launchpad-buildd, > but it should still be possible to fix this: make sure that the test > suite cleans up all its processes on exit, which is something that > should be actionable with a bit of care. it wouldn't surprise me if there are indeed processes still hanging around due to modern GnuPG's multi-process model (with dirmngr and gpg-agent getting launched as-needed). If you're doing the build on a modern linux system, and you haven't explicitly disabled the GnuPG's inotify support, and the test suite deletes any temporary GNUPGHOME homedirs, the subprocesses should notice the deletion and terminate promptly. This might depend on relatively recent versions of "modern" GnuPG, though (debian's currently shipping 2.1.17, fwiw). --dkg -- 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=/<>/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
Re: [Touch-packages] [Bug 1647204] [NEW] 1.8.0-2 FTBFS in zesty 17.04
iiuc, the hardening options for qgpgme need to match the hardening options for qtcore. if ubuntu is not setting at least the pie hardening option for qtcore, then it's missing out on the possibility of address space layout randomization (aslr) for many packages. I recommend that ubuntu should track debian's improvements in pie hardening for qt. --dkg -- 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: New 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=/<>/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
