From: Hartmut Goebel <h.goebel@crazy-compilers.com>
To: guix-devel@gnu.org
Subject: Re: [PATCH 1/2] gnu: python-2: Update to 2.7.11
Date: Tue, 26 Apr 2016 11:11:22 +0200 [thread overview]
Message-ID: <571F30BA.4030704@crazy-compilers.com> (raw)
In-Reply-To: <idjr3dy879r.fsf@bimsb-sys02.mdc-berlin.net>
Am 22.04.2016 um 08:52 schrieb Ricardo Wurmus:
> Rebuilding the Python package would result in a forced rebuild of all
> dependent packages. Our build farm isn’t fast enough to rebuild that
> much in time, so we would have an uncomfortable window during which a
> lot of packages would have to be built from source. By having a
Thanks for the explanation, this is quite reasonable. I'll check core
updates the next time.
Regarding the bug-fix updates for Python: I'd not expect any problems,
since these updates are bug-fixes only and the byte-code does not change
within a series (2.7.x, 3.4.x). So grafting could be an option here, too.
--
Regards
Hartmut Goebel
| Hartmut Goebel | h.goebel@crazy-compilers.com |
| www.crazy-compilers.com | compilers which you thought are impossible |
next prev parent reply other threads:[~2016-04-26 9:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-21 20:18 [PATCH 0/2] Update Python to current versions Hartmut Goebel
2016-04-21 20:18 ` [PATCH 1/2] gnu: python-2: Update to 2.7.11 Hartmut Goebel
2016-04-21 21:20 ` Efraim Flashner
2016-04-22 6:42 ` Hartmut Goebel
2016-04-22 6:52 ` Ricardo Wurmus
2016-04-26 9:11 ` Hartmut Goebel [this message]
2016-04-27 12:19 ` Ludovic Courtès
2016-04-21 20:18 ` [PATCH 2/2] gnu: python: Update to 3.4.4 Hartmut Goebel
2016-04-21 23:12 ` [PATCH 0/2] Update Python to current versions Cyril Roelandt
2016-04-22 1:57 ` Efraim Flashner
2016-04-22 6:41 ` Hartmut Goebel
2016-04-24 0:18 ` Leo Famulari
2016-04-24 21:43 ` Ludovic Courtès
2016-04-25 19:07 ` Leo Famulari
2016-04-26 9:28 ` Hartmut Goebel
2016-04-27 16:55 ` Leo Famulari
2016-04-27 18:05 ` Hartmut Goebel
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=571F30BA.4030704@crazy-compilers.com \
--to=h.goebel@crazy-compilers.com \
--cc=guix-devel@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 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.