unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Marius Bakke <mbakke@fastmail.com>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: core-updates: Python build failures
Date: Sun, 12 Mar 2017 18:44:56 +0100	[thread overview]
Message-ID: <87efy2jso7.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <20170312000509.GA28022@jasmine>

[-- Attachment #1: Type: text/plain, Size: 770 bytes --]

Leo Famulari <leo@famulari.name> writes:

> On Sat, Mar 11, 2017 at 08:50:32PM +0100, Marius Bakke wrote:
>> I tried applying the upstream fix for 3.5:
>> 
>> https://hg.python.org/cpython/rev/337461574c90
>> 
>> However, the monster patch does not apply.
>
> [...]
>
>> Will try to dig out the other patches from 3.5 branch that this depends
>> on tomorrow. I can't reproduce the getentropy() failure either,
>> apparently it only occurs on kernels < 3.17.
>
> Maybe we should update Python 3.5 instead, so that the patch applies. Or
> update the kernels on the build farm machines.

Oh, I missed that 3.5.3 is out. After updating, the patch applied.

I've pushed the Python update and the getentropy() fix as
343cee8af and e4d34cd0 respectively.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  reply	other threads:[~2017-03-12 17:45 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-14  9:05 Let’s freeze and build ‘core-updates’! Ludovic Courtès
2017-02-14 15:00 ` Marius Bakke
2017-02-14 16:22   ` Ludovic Courtès
2017-02-21 14:03     ` Marius Bakke
2017-02-21 16:27       ` Andreas Enge
2017-02-21 17:32       ` Leo Famulari
2017-02-21 17:41         ` Leo Famulari
2017-03-06  9:19           ` Ludovic Courtès
2017-03-06 12:31             ` Marius Bakke
2017-03-06 15:39               ` Ludovic Courtès
2017-03-06 22:26                 ` Leo Famulari
2017-03-07 13:59                   ` Ludovic Courtès
2017-03-08  5:43                     ` Leo Famulari
2017-03-08  8:44                       ` Ludovic Courtès
2017-03-08  9:03                         ` Leo Famulari
2017-03-06 18:42             ` Leo Famulari
2017-03-06 18:49               ` Marius Bakke
2017-03-06 18:54                 ` Marius Bakke
2017-03-06 19:13                   ` Leo Famulari
2017-03-06 18:54                 ` Leo Famulari
2017-02-27 20:30 ` core-updates frozen! Leo Famulari
2017-03-02 17:34   ` Leo Famulari
2017-03-03  0:02     ` Marius Bakke
2017-03-03 18:27       ` Leo Famulari
2017-03-03 18:33         ` Marius Bakke
2017-03-03 18:53           ` Leo Famulari
2017-03-09 22:33 ` Let’s freeze and build ‘core-updates’! Leo Famulari
2017-03-10 21:46   ` Marius Bakke
2017-03-11  3:10     ` Leo Famulari
2017-03-11 17:21     ` core-updates: Python build failures Leo Famulari
2017-03-11 19:50       ` Marius Bakke
2017-03-12  0:05         ` Leo Famulari
2017-03-12 17:44           ` Marius Bakke [this message]
2017-03-13  8:30             ` Ludovic Courtès
2017-03-20 18:41 ` Let’s freeze and build ‘core-updates’! Leo Famulari
2017-03-21 11:16   ` julien lepiller
2017-03-21 17:52     ` Leo Famulari
2017-03-21 21:19   ` Julien Lepiller
2017-03-21 22:02     ` Leo Famulari
2017-03-21 22:02     ` Ricardo Wurmus
2017-03-23 11:08   ` Thomas Danckaert
2017-03-23 12:38     ` Ricardo Wurmus
2017-03-29 13:41   ` Marius Bakke
2017-03-29 14:05     ` Marius Bakke
2017-03-29 20:49     ` Leo Famulari
2017-03-29 20:51     ` Leo Famulari
2017-03-30  6:23     ` Ricardo Wurmus
2017-03-30  8:36       ` Ricardo Wurmus
2017-03-30  9:18     ` Thomas Danckaert
2017-04-01 22:30     ` Ludovic Courtès
2017-04-01 23:09       ` Leo Famulari
2017-04-03  7:43         ` Ricardo Wurmus
2017-04-02 15:20       ` Marius Bakke
2017-04-02 15:42         ` Ricardo Wurmus
2017-04-02 21:23           ` Marius Bakke
2017-04-02 21:18         ` Marius Bakke
2017-04-02 22:39           ` ‘core-updates’ merged! Ludovic Courtès
2017-04-02 21:20         ` Greenisland & SDDM Ludovic Courtès
2017-04-02 21:31           ` Marius Bakke
2017-04-02 22:12             ` Ludovic Courtès

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=87efy2jso7.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me \
    --to=mbakke@fastmail.com \
    --cc=guix-devel@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).