subject:"\[Touch\-packages\] \[Bug 1647204\] Re\: 1.8.0\-2 FTBFS in zesty 17.04"

Uploaded.  Now we just have to get the archive admins to let it pass now
that we've entered feature freeze, if that's even a good idea.

-- 
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

[Touch-packages] [Bug 1647204] Re: 1.8.0-2 FTBFS in zesty 17.04

Testing LGTM.  Thanks very much for the patch.  I will sponsor it.

-- 
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

[Touch-packages] [Bug 1647204] Re: 1.8.0-2 FTBFS in zesty 17.04

So far so good:
https://launchpad.net/~barry/+archive/ubuntu/experimental/+packages

I'm going to test encryption with claws-mail in a VM.  If that looks
good too, I'll sponsor gpgme1.0 with your patch.

-- 
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

[Touch-packages] [Bug 1647204] Re: 1.8.0-2 FTBFS in zesty 17.04

@panfaust: the patch looks pretty reasonable.  I'll give it a try in my
ppa, which builds all arches except powerpc and s390x.

-- 
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

[Touch-packages] [Bug 1647204] Re: 1.8.0-2 FTBFS in zesty 17.04

2017-02-19 Thread Mathew Hodson

** Changed in: gpgme1.0 (Ubuntu)
   Importance: Undecided => High

-- 
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

[Touch-packages] [Bug 1647204] Re: 1.8.0-2 FTBFS in zesty 17.04

2017-02-18 Thread Jose Manuel Santamaria Lema

Hi again, I think I'm done now with a proposal for upload, the package was
tested in this PPA:
https://launchpad.net/~panfaust/+archive/ubuntu/gpgme

Note that I also tested a rebuild of kf5-kdepim-apps-libs against it; right now
kf5-kdepim-apps-libs is failing against the current version in -proposed,
making some autopkgtests fail and blocking the migration of some kde libraries.
See, for instance:
https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#kiconthemes

So we would really appreciate if someone could upload this fixed
package.

If you think the proposed fix can be improved, suggestions are welcomed
:)

** Patch added: "Package upload roposal"

https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/1647204/+attachment/4821728/+files/gpgme1.0_1.8.0-3ubuntu2.debdiff

--
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

[Touch-packages] [Bug 1647204] Re: 1.8.0-2 FTBFS in zesty 17.04

2017-02-18 Thread Jose Manuel Santamaria Lema

Hi,

> No, that's not really acceptable. firstly +pic is not an hardening option 
> AFAIK, what you 
> effectively did was disabling pie. Then I don't particularly like disabling 
> tests just because
> they hang; please somebody investigate why they hang and actually fix them.

> Unsubscribing sponsors for now.


I just wanted to say that the package I had in my kde-test-good PPA was just an 
experiment, nothing actually intended to be uploaded. Before finishing 
completely the fixing of this, I had to pause for a while my work on Ubuntu 
(I'm sorry about that).

After catching up again with the work I was doing I see the problems I
spotted initially (the entropy starvation and the tests hanging) were
solved, thank you!

However there are still at least a couple of problems more with this package. 
Right now, I'm doing some experiments here:
https://launchpad.net/~panfaust/+archive/ubuntu/gpgme/

Yes, it's not something acceptable for uploading for now! But I hope to
get something finished soon.

Cheers.

-- 
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

2017-02-14 Thread Rik Mills

On 10/02/17 09:48, Andre Heinecke wrote:
> Ah but now armhf and arm64 fail because of the same problem. The
> connects in the Qt Testsuite fail.
> 
> As I already mentioned I think its some incompatibility between the Qt
> buildflags and the QGpgME buildflags:
> 
> https://bugreports.qt.io/browse/QTBUG-36129 but I'm not sure what the
> suggestion from this should be. Adding pie to the compile flags? Or
> removing the -Bsymbolic-functions (Debian does not use that flag). I
> don't have much knowledge on these kinds of problems.

thiago = Thiago Macieira (from your buglink)

#kde-devel on irc.freenode.net

[20:59]  acheronuk: any chance you can get me the build logs in
the actual server?
[20:59]  if the -Bsymbolic-functions argument is there, that's
the reason
[20:59]  that option is ABI-incompatible outside
strictly-controlled environments
[21:00]  it should be opt-in, not opt-out
[21:03]  all I have
https://launchpadlibrarian.net/305535133/buildlog_ubuntu-zesty-arm64.gpgme1.0_1.8.0+git20170207-0build1_BUILDING.txt.gz
[21:23]  acheronuk: thanks
[21:24]  acheronuk: /bin/bash ../../../libtool  --tag=CXX
--mode=link g++ [...]  -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,-z,now
-o libqgpgme.la [...]
[21:24]  culprit found
[21:25]  thiago: that log file seems to be full of
-Bsymbolic-functions
[21:25]  it is
[21:26]  the one that matters is the one I pasted: libqgpgme.so
was linked with it
[21:27]  the debian build log does not look like it contains that
[21:28]  as I said, outside of x86-64, you have to make it opt-in
[21:28]  thiago: thx. now I have to work out how to get rid
of that without nuking the rest of the build
[21:29]  acheronuk: talk to your toolchain maintainers
[21:29]  I guess that's where it is injected
[21:32]  acheronuk: nuke the rest of the build and rebuild the world
[21:33]  I'm not kidding
[21:33]  rebuild the world
[21:33]  if your toolchain people don't like the change, they
can join the club. I've been trying to get GCC+binutils folks to do
something about unnecessary ELF interposition for some time

How to achieve a working solution is something I still don't know
though.

For my purposes, I care very little if arm* builds break/fail, but is
obviously an issue for others, and regards getting this out of
'-proposed' wilderness.

-- 
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

[Touch-packages] [Bug 1647204] Re: 1.8.0-2 FTBFS in zesty 17.04

2017-02-10 Thread Andre Heinecke

Ah but now armhf and arm64 fail because of the same problem. The
connects in the Qt Testsuite fail.

As I already mentioned I think its some incompatibility between the Qt
buildflags and the QGpgME buildflags:

https://bugreports.qt.io/browse/QTBUG-36129 but I'm not sure what the
suggestion from this should be. Adding pie to the compile flags? Or
removing the -Bsymbolic-functions (Debian does not use that flag). I
don't have much knowledge on these kinds of problems.

Maybe you could look at some Tier 0 KDE Framework and check what they
are using as compile flags? They should have similar problems.

-- 
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

2017-02-07 Thread Rik Mills

On 30/01/17 13:27, Andre Heinecke wrote:
> I've discussed possibly high resource usage of the gpgme test suite
> (there were also other complaints) and we reduced it accordingly:
> https://git.gnupg.org/cgi-
> bin/gitweb.cgi?p=gpgme.git;a=commitdiff;h=7bd6ab4a91d43d7cbf5d347c0c12e0e4f9f7e3bf
> 
> This might fix the armhf error in t-thread-keylist-verify

I tried building today's git snapshot, and still get test failures on
armhf and arm64

https://launchpad.net/~rikmills/+archive/ubuntu/staging1/+sourcepub/7468978
/+listing-archive-extra

I can't test powerpc in a ppa.

-- 
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 Jan 30, 2017, at 04:42 PM, Rik Mills wrote:

>Ummm. If you are Ok with that FTBFS still on arm64 and armhf, then ok.

Dang.  Well, we'll have to deal with that next.

-- 
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

2017-01-30 Thread Rik Mills

On 30/01/17 16:23, Barry Warsaw wrote:
> The PPA build is looking good.  I'll check autopkgtests next and if that
> all looks good, I'll sponsor your debdiff.  Thanks!

Ummm. If you are Ok with that FTBFS still on arm64 and armhf, then ok.

-- 
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

[Touch-packages] [Bug 1647204] Re: 1.8.0-2 FTBFS in zesty 17.04

All looks good, so I'm uploading.  Thanks very much for all the help!

-- 
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

[Touch-packages] [Bug 1647204] Re: 1.8.0-2 FTBFS in zesty 17.04

The PPA build is looking good.  I'll check autopkgtests next and if that
all looks good, I'll sponsor your debdiff.  Thanks!

-- 
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 Jan 30, 2017, at 09:42 AM, Rik Mills wrote:

>** Patch added: "gpgme1.0_1.8.0-3ubuntu1.debdiff"
>   
> https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/1647204/+attachment/4810708/+files/gpgme1.0_1.8.0-3ubuntu1.debdiff

Thanks for the debdiff.  LGTM; building in my PPA.  If it passes, I'll sponsor
this.  You might consider reporting this bug (and attaching the debdiff) to
Debian since we'll need to resync the package at some point.

-- 
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

2017-01-30 Thread Rik Mills

On 30/01/17 13:27, Andre Heinecke wrote:
> I've discussed possibly high resource usage of the gpgme test suite
> (there were also other complaints) and we reduced it accordingly:
> https://git.gnupg.org/cgi-
> bin/gitweb.cgi?p=gpgme.git;a=commitdiff;h=7bd6ab4a91d43d7cbf5d347c0c12e0e4f9f7e3bf
> This might fix the armhf error in t-thread-keylist-verify

Applied as a patch to v1.8, the first hunk of that modifying
/tests/gpg/t-gpgconf.c fails to apply due to other commits since v1.8.

I am not 100% certain if it is redundant on the older revision, or not.

> Is there still something open here that would block GpgME-1.8 from
> making it into ubuntu?

Presumably the Qt test issue for arm64 would still exist, although from
my perspective that is not critical, or maybe fixable later.

Whether it would block things, I am not sure.

> Otherwise we'll probably also release a new GpgME Version including
> these changes soon.

That would be good.

-- 
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

[Touch-packages] [Bug 1647204] Re: 1.8.0-2 FTBFS in zesty 17.04

2017-01-30 Thread Andre Heinecke

I don't think Barry included the patch against entropy starvation in his
PPA so It's expected that it would hang.

I've discussed possibly high resource usage of the gpgme test suite
(there were also other complaints) and we reduced it accordingly:
https://git.gnupg.org/cgi-
bin/gitweb.cgi?p=gpgme.git;a=commitdiff;h=7bd6ab4a91d43d7cbf5d347c0c12e0e4f9f7e3bf

This might fix the armhf error in t-thread-keylist-verify

Is there still something open here that would block GpgME-1.8 from
making it into ubuntu?

Otherwise we'll probably also release a new GpgME Version including
these changes soon.

-- 
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

[Touch-packages] [Bug 1647204] Re: 1.8.0-2 FTBFS in zesty 17.04

2017-01-30 Thread Rik Mills

Barry: The build with your patch seemed to hang again, and be killed on
LP timeout.

This one builds in my ppa.


** Patch added: "gpgme1.0_1.8.0-3ubuntu1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/1647204/+attachment/4810708/+files/gpgme1.0_1.8.0-3ubuntu1.debdiff

-- 
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

[Touch-packages] [Bug 1647204] Re: 1.8.0-2 FTBFS in zesty 17.04

2017-01-26 Thread Barry Warsaw

** Patch added: "lp1647204.diff"
   
https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/1647204/+attachment/4809525/+files/lp1647204.diff

-- 
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

[Touch-packages] [Bug 1647204] Re: 1.8.0-2 FTBFS in zesty 17.04

2017-01-26 Thread Barry Warsaw

Thanks; I'm testing this in my own PPA now.  If it succeeds, then I'm
happy to upload this to Zesty.  I have my own patch, which I'll attach
here, but I'm also happy to sponsor a fix authored by you if you want to
attach a debdiff to apply to the Zesty package.  Or, if you are an
Ubuntu developer, don't wait for me!

-- 
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

[Touch-packages] [Bug 1647204] Re: 1.8.0-2 FTBFS in zesty 17.04

2017-01-26 Thread Andre Heinecke

Regarding the armhf failure in t-thread-keylist-verify This is a test
for a race condition bug we had in the past. It's fairly resource
intensive so maybe it runs into resource problems on the armhf builder.
Maybe we can just reduce the number of threads there or disable the
test.

Regarding the arm64 failure. The Qt tests use new style connects and
lambdas googling a bit brought me to
https://bugreports.qt.io/browse/QTBUG-36129 but I'm not sure what the
suggestion from this should be. Adding pie to the compile flags? Or
removing the -Bsymbolic-functions (Debian does not use that flag).

Maybe someone from a KDE Packaging team can help here because this
probably is not a QGpgME specific issue.

-- 
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

2017-01-26 Thread Rik Mills

On 26/01/17 10:26, Andre Heinecke wrote:
> I've tested in a personal ppa and with this patch it successfully compiled:
> https://launchpad.net/~aheinecke/+archive/ubuntu/gpgme-test
> 
> Sorry for the extra work.
> 

Thank you :)

Rebuilt that in my ppa, and while the 5 (out of 7) archive architectures
I can test on now get past the hang and complete their test, armhf &
arm64 builds fail the tests and so fail the build.

These passed when building on debian for those architectures as far as I
can see.

-- 
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

[Touch-packages] [Bug 1647204] Re: 1.8.0-2 FTBFS in zesty 17.04

2017-01-26 Thread Andre Heinecke

Indeed my fix was incomplete, according to your build log the gpg-agent
for the python tests is already running when the modified start-stop-
agent script is called so it was still started without debug quick
random.

This was because in difference to my local system gpg is gpg2.1 and not
gpg1 so the environment setup for the python scripts already launches
the agent when importing secret keys.

The additional fix for that is:
https://git.gnupg.org/cgi-bin/gitweb.cgi?p=gpgme.git;a=commitdiff;h=f3ca2c9ce9fd4a03e293065f10b92589a7e642d6

I've tested in a personal ppa and with this patch it successfully compiled:
https://launchpad.net/~aheinecke/+archive/ubuntu/gpgme-test

Sorry for the extra work.

--
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.

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

2017-01-25 Thread Rik Mills

On 25/01/17 13:22, Andre Heinecke wrote:
> I've changed the start script of the gpg-agent in gpgme accordingly
> with:
> 
> https://git.gnupg.org/cgi-
> bin/gitweb.cgi?p=gpgme.git;a=commitdiff;h=a98951a30a6ae603ffac4ec8c5168aa6d1019933
> 
> To also use that option. Please confirm if this fixes the Problem in
> your build environment.
> 

Applied the patch to 1.8.0-3, and does not seem to have made any
difference.

am64, i386 and armhf builds still hang at the same point and are killed
by launchpad with

"Build killed with signal TERM after 150 minutes of inactivity"

arm64 build just fails somewhere, and LP fails to render a buildlog for
some strange reason

ppc64el, as it did before, hangs for a bit then completes ok.

-- 
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

[Touch-packages] [Bug 1647204] Re: 1.8.0-2 FTBFS in zesty 17.04

2017-01-25 Thread Andre Heinecke

> https://www.python.org/dev/peps/pep-0524/

This has nothing to do with it. GpgME does not gather the entropy /
randomness itself but leaves this to libgcrypt / gpg-agent. On Linux
system this means to add some entropy from /dev/random into the mix. If
nothing is available there it will block indefinitely until enough
entropy is available.

So I agree with dkg's suggestion that a lack of entropy in your build 
environments is a likely explanation.
I can reproduce a fairly long hang by starving my system of entropy using "cat 
/dev/random > /dev/null" and then running make check.

It could be worked around by something like "rngd -r /dev/urandom" but
the testsuite should not rely on hard entropy. GnuPG's testsuite itself
includes a solution to that problem, launching gpg-agent with --debug-
quick-random.

I've changed the start script of the gpg-agent in gpgme accordingly
with:

https://git.gnupg.org/cgi-
bin/gitweb.cgi?p=gpgme.git;a=commitdiff;h=a98951a30a6ae603ffac4ec8c5168aa6d1019933

To also use that option. Please confirm if this fixes the Problem in
your build environment.

-- 
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

2017-01-13 Thread Barry Warsaw

On Jan 13, 2017, at 09:26 PM, dkg wrote:

>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?

Oh, oh.  I wonder if you're getting bitten by PEP 524

https://www.python.org/dev/peps/pep-0524/

I don't believe this was back ported to Python 3.5 or 2.7 though.

-- 
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

2017-01-13 Thread dkg

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

[Touch-packages] [Bug 1647204] Re: 1.8.0-2 FTBFS in zesty 17.04

2017-01-13 Thread Rik Mills

Seems that even completely disabling the hanging tests is not enough
now. Doing that results in failing tests on arm64 and armhf.

amd64, i386 and ppc64el pass

As in this build https://launchpad.net/~rikmills/+archive/ubuntu
/staging-kde-apps-16.12/+sourcepub/7397892/+listing-archive-extra

-- 
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 Jan 12, 2017, at 10:49 PM, Rik Mills wrote:

>ppc64el hung for nearly that whole time, then for some bizarre reason
>decided to complete. Not seen that before.

That sure is weird.

-- 
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 12/01/17 21:52, Barry Warsaw wrote:
> Any results yet?

[FAILEDTOBUILD] amd64
[FAILEDTOBUILD] arm64
[FAILEDTOBUILD] armhf
[FAILEDTOBUILD] i386
[FULLYBUILT] ppc64el

Failures hung in the usual place and were killed by LP after 2 hours 40
minutes

ppc64el hung for nearly that whole time, then for some bizarre reason
decided to complete. Not seen that before.

-- 
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

[Touch-packages] [Bug 1647204] Re: 1.8.0-2 FTBFS in zesty 17.04

As I also commented in Bug #1655298 :

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.

# Test the progress callback.
parms = """
Key-Type: RSA
Key-Length: 1024
Name-Real: Joe Tester
Name-Comment: with stupid passphrase
Name-Email: joe+...@example.org
Passphrase: Crypt0R0cks
Expire-Date: 2020-12-31

"""

messages = []
def progress_cb(what, typ, current, total, hook=None):
assert hook == messages
messages.append(
"PROGRESS UPDATE: what = {}, type = {}, current = {}, total = {}"
.format(what, typ, current, total))

c = gpg.Context()
c.set_progress_cb(progress_cb, messages)
c.op_genkey(parms, None, None) < HANGS HERE
assert len(messages) > 0

# Test exception handling.
def progress_cb(what, typ, current, total, hook=None):
raise myException

c = gpg.Context()
c.set_progress_cb(progress_cb, None)
try:
c.op_genkey(parms, None, None) < HANGS HERE
except Exception as e:
assert e == myException
else:
assert False, "Expected an error, got none"

-- 
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

[Touch-packages] [Bug 1647204] Re: 1.8.0-2 FTBFS in zesty 17.04

Sorry, I did a 2nd build as something odd happened in the arm64 builder
of the 1st.

As you rightly say, they just hand now and will be killed by L.

Manually cancelling a build reveals some more about what what happening
at the time. see below:

This agree with other diagnostic builds I did which show the hanging
call is

c.op_genkey(parms, None, None)


-- Log from manually cancelled build 

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 
RUN: /usr/share/launchpad-buildd/slavebin/scan-for-processes 
['scan-for-processes', 'PACKAGEBUILD-11850388']
Scanning for processes to kill in build 
/home/buildd/build-PACKAGEBUILD-11850388/chroot-autobuild...
Traceback (most recent call last):
  File "./t-callbacks.py", line 105, in 
c.op_genkey(parms, None, None)
  File "/<>/lang/python/build/lib.linux-x86_64-2.7/gpg/core.py", 
line 151, in wrapper
return _funcwrap(self, *args)
  File "/<>/lang/python/build/lib.linux-x86_64-2.7/gpg/core.py", 
line 135, in _funcwrap
return errorcheck(result, "Invocation of " + name)
  File "/<>/lang/python/build/lib.linux-x86_64-2.7/gpg/errors.py", 
line 62, in errorcheck
raise GPGMEError(retval, extradata)
gpg.errors.GPGMEError: Invocation of gpgme_op_genkey: GnuPG: End of file

-- 
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 Jan 12, 2017, at 07:30 PM, Rik Mills wrote:

>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.

Any results yet?

Is it possible that the test suite tries to hit the internet?  And if it does
but external hosts are unavailable, what's the failure mode?

That's another difference between local builds and the Launchpad buildds.  The
latter do not allow access to the internet.

This probably isn't it though.  I added a patch to set `offline=True` to the
Context constructor and while it hasn't been killed yet, a PPA build of mine
still appears hung.  Just thought I'd mention it.

-- 
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 12/01/17 19:38, Barry Warsaw wrote:
> This diff gets past the build failure:
> 

It does, but sadly still FTBFS or hangs in tests when built on launchapd

-- 
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

[Touch-packages] [Bug 1647204] Re: 1.8.0-2 FTBFS in zesty 17.04

This diff gets past the build failure:

1 file changed, 1 insertion(+), 1 deletion(-)
debian/rules | 2 +-

modified   debian/rules
@@ -1,6 +1,6 @@
 #!/usr/bin/make -f
 
-export DEB_BUILD_MAINT_OPTIONS = hardening=+all
+export DEB_BUILD_MAINT_OPTIONS = hardening=+all,-pie,+pic
 export QT_SELECT := qt5
 export DEBIAN_VERSION = $(shell dpkg-parsechangelog | sed -n -e 
'/^Version:/s/.*: //p')
 

[back]

-- 
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 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=/<>/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

[Touch-packages] [Bug 1647204] Re: 1.8.0-2 FTBFS in zesty 17.04