From: Kei Kebreau <kkebreau@posteo.net>
To: Mark H Weaver <mhw@netris.org>
Cc: guix-devel@gnu.org
Subject: Re: 01/01: gnu: python-pillow: Fix test failures on i686-linux and armhf-linux.
Date: Sat, 30 Dec 2017 18:43:14 -0500 [thread overview]
Message-ID: <87y3ljvl2l.fsf@posteo.net> (raw)
In-Reply-To: <87bmiislvy.fsf@netris.org> (Mark H. Weaver's message of "Thu, 28 Dec 2017 14:17:05 -0500")
[-- Attachment #1: Type: text/plain, Size: 1142 bytes --]
Mark H Weaver <mhw@netris.org> writes:
> kkebreau@posteo.net (Kei Kebreau) writes:
>
>> kkebreau pushed a commit to branch master
>> in repository guix.
>>
>> commit 15b60fc3138e9d601aff3e3317373ed465e6ea93
>> Author: Kei Kebreau <kkebreau@posteo.net>
>> Date: Sun Dec 24 16:23:50 2017 -0500
>>
>> gnu: python-pillow: Fix test failures on i686-linux and armhf-linux.
>>
>> * gnu/packages/patches/python-pillow-fix-failing-tests.patch: New file.
>> * gnu/local.mk (dist_patch_DATA): Add it.
>> * gnu/packages/python.scm (python-pillow)[source]: Use it.
>
> Thanks for your efforts, but after this commit, Hydra still failed to
> build both python-pillow and python2-pillow on i686 and armhf:
>
> https://hydra.gnu.org/eval/109870?filter=pillow
>
> Mark
I've included more fixes from upstream from the related pull request[0]
in the patch provided under bug #29912. While I can't test the
armhf-linux build, on my machine the i686-linux and x86_64-linux versions
of python-pillow and python2-pillow build without a problem.
[0]: https://github.com/python-pillow/Pillow/pull/2825
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
prev parent reply other threads:[~2017-12-30 23:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20171227170813.11009.20833@vcs0.savannah.gnu.org>
[not found] ` <20171227170818.E6B1420812@vcs0.savannah.gnu.org>
2017-12-28 19:17 ` 01/01: gnu: python-pillow: Fix test failures on i686-linux and armhf-linux Mark H Weaver
2017-12-30 23:43 ` Kei Kebreau [this message]
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=87y3ljvl2l.fsf@posteo.net \
--to=kkebreau@posteo.net \
--cc=guix-devel@gnu.org \
--cc=mhw@netris.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).