all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Christopher Allan Webber <cwebber@dustycloud.org>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: Python 3.5 start of update
Date: Tue, 30 Aug 2016 09:03:41 -0500	[thread overview]
Message-ID: <877fay8ibm.fsf@dustycloud.org> (raw)
In-Reply-To: <20160830014810.GA12517@jasmine>

Leo Famulari writes:

> On Sun, Aug 21, 2016 at 01:58:51PM -0400, Leo Famulari wrote:
>> I picked this up. I've attached two patches. They upgrade python-3.4 to
>> 3.4.5, and then upgrade python-3 to 3.5.2 while preserving a python-3.4.
>> These are the latest releases in their respective series.
>> 
>> I had to split part of the python-fix-tests.patch into 3.4 and 3.5
>> specific patches, since those packages' codebases have diverged.
>> 
>> python@3.4.5 and python@3.5.2 both build on master and wip-python.
>> python-setuptools builds with python@3.5.2 on master.
>> 
>> I'd like to put these on core-updates. The wip-python branch will take a
>> while to get ready. I found this saga about what Nix had to do to
>> upgrade setuptools:
>> https://github.com/NixOS/nixpkgs/pull/12552
>
> I went ahead and pushed to core-updates, bringing the branch to
> 72df66806.

Horray!  Thanks for pushing it the rest of the way. :)

      reply	other threads:[~2016-08-30 14:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-27  5:19 Python 3.5 start of update Diane Trout
2016-03-04  3:15 ` Leo Famulari
2016-03-05  6:51   ` Diane Trout
2016-03-08  6:52     ` Diane Trout
2016-03-08  8:24       ` Ricardo Wurmus
2016-06-21 15:44       ` Christopher Allan Webber
2016-06-21 21:29         ` Ludovic Courtès
2016-06-22 13:15           ` Christopher Allan Webber
2016-08-21 17:58             ` Leo Famulari
2016-08-30  1:48               ` Leo Famulari
2016-08-30 14:03                 ` Christopher Allan Webber [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=877fay8ibm.fsf@dustycloud.org \
    --to=cwebber@dustycloud.org \
    --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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.