From: Kei Kebreau <kei@openmailbox.org>
To: Leo Famulari <leo@famulari.name>
Cc: 27827-done@debbugs.gnu.org
Subject: [bug#27827] [PATCH] gnu: python2-urwid: Actually build urwid for Python 2.
Date: Wed, 02 Aug 2017 16:45:21 -0400 [thread overview]
Message-ID: <87bmnx4s2m.fsf@openmailbox.org> (raw)
In-Reply-To: <20170725194250.GA28267@jasmine.lan> (Leo Famulari's message of "Tue, 25 Jul 2017 15:42:50 -0400")
[-- Attachment #1: Type: text/plain, Size: 913 bytes --]
Leo Famulari <leo@famulari.name> writes:
> On Tue, Jul 25, 2017 at 03:30:51PM -0400, Kei Kebreau wrote:
>> Leo Famulari <leo@famulari.name> writes:
>>
>> > On Tue, Jul 25, 2017 at 02:50:16PM -0400, Kei Kebreau wrote:
>> >> * gnu/packages/python.scm (python2-urwid)[arguments]: Add #:python.
>> >
>> > Good catch! I didn't test this change with `guix gc --references`, but
>> > if that shows the right thing your end, please push!
>>
>> Yes, python2-urwid shows up now. Prior to the patch it did not.
>>
>> Pushed to master! Thanks again for the review.
>
> I just tested it, and it fails to build for me. But, I've noticed the
> urwid test suite is pretty flaky. Let's see if it builds on Hydra.
I've since updated my system and wicd-curses still works. Does it build
on Hydra? I haven't been able to check because of 504 HTTP response
codes from https://hydra.gnu.org most of the time.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2017-08-02 20:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-25 18:50 [bug#27827] [PATCH] gnu: python2-urwid: Actually build urwid for Python 2 Kei Kebreau
2017-07-25 19:21 ` Leo Famulari
2017-07-25 19:30 ` bug#27827: " Kei Kebreau
2017-07-25 19:42 ` [bug#27827] " Leo Famulari
2017-08-02 20:45 ` Kei Kebreau [this message]
2017-08-02 22:47 ` Leo Famulari
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=87bmnx4s2m.fsf@openmailbox.org \
--to=kei@openmailbox.org \
--cc=27827-done@debbugs.gnu.org \
--cc=leo@famulari.name \
/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).