On Thu 2017-02-23 16:57:12 -0500, Launchpad Bug Tracker wrote:
> * Add in libgpgme-dev a libgpgme-pthread.so pointing to libgpgme.so, this
> will fix the build failures of kf5-kdepim-apps-libs when built against
> this
> gpgme package.
As i wrote when asked on IRC, i think this is the
This bug was fixed in the package gpgme1.0 - 1.8.0-3ubuntu2
---
gpgme1.0 (1.8.0-3ubuntu2) zesty; urgency=medium
* Add in libgpgme-dev a libgpgme-pthread.so pointing to libgpgme.so, this
will fix the build failures of kf5-kdepim-apps-libs when built against this
gpgme
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1647204
Title:
Testing LGTM. Thanks very much for the patch. I will sponsor it.
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1647204
Title:
1.8.0-2 FTBFS in zesty 17.04
To manage notifications about
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
Bugs, which is
@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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1647204
Title:
1.8.0-2
** Changed in: gpgme1.0 (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1647204
Title:
1.8.0-2 FTBFS in zesty 17.04
To manage notifications about this bug
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
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
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:
>
>
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
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
>
>
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
Bugs, which is subscribed to Ubuntu.
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
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1647204
Title:
1.8.0-2 FTBFS in zesty 17.04
To manage notifications about this
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1647204
Title:
1.8.0-2
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,
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
>
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-
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
--
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,
** 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1647204
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
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
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
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
> 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
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
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
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
--
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
Bugs, which is subscribed to Ubuntu.
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
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
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:
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
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
Bugs, which is subscribed to Ubuntu.
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 :=
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
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.
--
You received this bug notification because you are a member
The issue with the buildd hang is now reported against launchpad-builds
as:
Bug #1655298 - Indefinite build hangs during python tests of gpgme1.0
v1.8
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
On 31/12/16 01:19, Colin Watson wrote:
> Sounds like the problem is that this build leaves processes hanging
> around from its tests. Unfortunately this currently causes builds to
> hang, basically because launchpad-buildd uses sbuild's sudo mode rather
> than its schroot mode. So the hang is a
On Fri 2016-12-30 20:19:04 -0500, Colin Watson wrote:
> Sounds like the problem is that this build leaves processes hanging
> around from its tests. Unfortunately this currently causes builds to
> hang, basically because launchpad-buildd uses sbuild's sudo mode rather
> than its schroot mode. So
Sounds like the problem is that this build leaves processes hanging
around from its tests. Unfortunately this currently causes builds to
hang, basically because launchpad-buildd uses sbuild's sudo mode rather
than its schroot mode. So the hang is a known bug in launchpad-buildd,
but it should
** Patch removed: "gpgme1.0_1.8.0-3ubuntu1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/1647204/+attachment/4797029/+files/gpgme1.0_1.8.0-3ubuntu1.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Unfortunately it is only on the ubuntu build system that the test in
question seems to hang. On debian's build system, and local
pbuilder/sbuild chroot and straight from source, the tests complete
without issue. So I am unable to investigate the cause further.
--
You received this bug
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.
The attachment "gpgme1.0_1.8.0-3ubuntu1.debdiff" seems to be a debdiff.
The ubuntu-sponsors team has been subscribed to the bug report so that
they can review and hopefully sponsor the debdiff. If the attachment
isn't a patch, please remove the "patch" flag from the attachment,
remove the "patch"
Looking at the testing work Jose did a couple of weeks ago (and doesn't
seem to have come back to yet), his testing changes consolidate to
effectively the attached diff.
I am unsure if such changes are acceptable for a package upload, or if
they are only acceptable as diagnostic/troubleshooting
Seems the indefinite hang in running tests occurs in
lang/python/tests/t-callbacks.py
at the point where
c.op_genkey(parms, None, None)
is called in the '# Test the progress callback' and '# Test exception
handling' sections
--
You received this bug notification because you are a member of
I note that Jose has some apparently successful builds of 1.8.0-3 in the
following ppa
https://launchpad.net/~panfaust/+archive/ubuntu/kde-test-good
so I would like to enquire if the changes contained there are
acceptable, as if so can these be applied to the ubuntu archive package
to enable
** Changed in: gpgme1.0 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1647204
Title:
1.8.0-2 FTBFS in zesty 17.04
To manage notifications about this bug go
** Tags added: ftbfs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1647204
Title:
1.8.0-2 FTBFS in zesty 17.04
To manage notifications about this bug go to:
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.
Subscribing kubuntu in that case
** Tags added: kubuntu
53 matches
Mail list logo
