From: Leo Famulari <leo@famulari.name>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Fix python-pygpgme FTBFS [was Re: Let’s fix build failures on ‘staging’!]
Date: Sat, 7 Jan 2017 16:46:27 -0500 [thread overview]
Message-ID: <20170107214627.GA27722@jasmine> (raw)
In-Reply-To: <87zij2y2to.fsf@gnu.org>
On Sat, Jan 07, 2017 at 10:31:31PM +0100, Ludovic Courtès wrote:
> Leo Famulari <leo@famulari.name> skribis:
>
> > On Sat, Jan 07, 2017 at 12:50:33PM +0100, Ludovic Courtès wrote:
> >> • there’s 1 tests failure in python2-pygpgme (breaks many things)
> >> https://hydra.gnu.org/build/1752661
> >
> > I attached a patch that takes a patch from Debian to fix the test
> > failure. But I'm not sure if anything else is still broken in pygpgme.
>
> Woow, that was fast!
>
> > Also, AFAICT, only 'alot' uses python2-pygpgme. What else breaks?
>
> Nothing in fact (“alot” and “many things” are kinda synonymous? ;-)).
;)
> > From 706934ec0765fa3adbf71d84a27cadfdd1c892b3 Mon Sep 17 00:00:00 2001
> > From: Leo Famulari <leo@famulari.name>
> > Date: Sat, 7 Jan 2017 12:11:45 -0500
> > Subject: [PATCH] gnu: python-pygpgme: Fix build failure.
> >
> > * gnu/packages/patches/python-pygpgme-fix-pinentry-tests.patch: New file.
> > * gnu/local.mk (dist_patch_DATA): Add it.
> > * gnu/packages/gnupg.scm (python-pygpgme, python2-pygpgme)[source]: Use it.
>
> LGTM, thank you!
Pushed!
next prev parent reply other threads:[~2017-01-07 21:46 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-23 5:23 Staging freeze Leo Famulari
2016-12-23 6:00 ` John Darrington
2016-12-26 18:16 ` Leo Famulari
2016-12-27 23:56 ` Leo Famulari
2016-12-28 4:13 ` Leo Famulari
2016-12-28 9:17 ` John Darrington
2016-12-29 17:16 ` Leo Famulari
2016-12-29 17:51 ` Ludovic Courtès
2016-12-29 18:42 ` Leo Famulari
2016-12-31 11:12 ` Ludovic Courtès
2017-01-04 8:45 ` Leo Famulari
2017-01-04 22:31 ` Ludovic Courtès
2017-01-07 11:50 ` Let’s fix build failures on ‘staging’! Ludovic Courtès
2017-01-07 17:15 ` Fix python-pygpgme FTBFS [was Re: Let’s fix build failures on ‘staging’!] Leo Famulari
2017-01-07 21:31 ` Ludovic Courtès
2017-01-07 21:46 ` Leo Famulari [this message]
2017-01-07 17:22 ` Let’s fix build failures on ‘staging’! Leo Famulari
2017-01-07 17:35 ` Leo Famulari
2017-01-07 21:32 ` Ludovic Courtès
2017-01-07 21:46 ` Leo Famulari
2017-01-08 17:19 ` Leo Famulari
2017-01-07 18:10 ` [PATCH 1/2] Revert "gnu: Add threaded variants of fftw and fftwf for Ardour and mod-host." David Craven
2017-01-07 18:10 ` [PATCH 2/2] gnu: ardour: Add eudev dependency David Craven
2017-01-07 19:11 ` [PATCH 1/2] Revert "gnu: Add threaded variants of fftw and fftwf for Ardour and mod-host." Ricardo Wurmus
2017-01-07 22:43 ` David Craven
2017-01-07 22:45 ` David Craven
2017-01-08 10:57 ` Ludovic Courtès
2017-01-08 7:23 ` Ricardo Wurmus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170107214627.GA27722@jasmine \
--to=leo@famulari.name \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).