From mboxrd@z Thu Jan  1 00:00:00 1970
From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=)
Subject: Re: [PATCH 1/2] gnu: python-2: Update to 2.7.11
Date: Wed, 27 Apr 2016 14:19:51 +0200
Message-ID: <877ffj4520.fsf@gnu.org>
References: <1461269926-7934-1-git-send-email-h.goebel@crazy-compilers.com>
	<1461269926-7934-2-git-send-email-h.goebel@crazy-compilers.com>
	<20160421212037.GA26547@debian-netbook>
	<5719C7EF.9090906@crazy-compilers.com>
	<idjr3dy879r.fsf@bimsb-sys02.mdc-berlin.net>
	<571F30BA.4030704@crazy-compilers.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Return-path: <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:58217)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <ludo@gnu.org>) id 1avORh-00044s-7Z
	for guix-devel@gnu.org; Wed, 27 Apr 2016 08:20:03 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <ludo@gnu.org>) id 1avORe-0008TQ-12
	for guix-devel@gnu.org; Wed, 27 Apr 2016 08:19:57 -0400
In-Reply-To: <571F30BA.4030704@crazy-compilers.com> (Hartmut Goebel's message
	of "Tue, 26 Apr 2016 11:11:22 +0200")
List-Id: "Development of GNU Guix and the GNU System distribution."
	<guix-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/guix-devel/>
List-Post: <mailto:guix-devel@gnu.org>
List-Help: <mailto:guix-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=subscribe>
Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
Sender: "Guix-devel" <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
To: Hartmut Goebel <h.goebel@crazy-compilers.com>
Cc: guix-devel@gnu.org

Hartmut Goebel <h.goebel@crazy-compilers.com> skribis:

> 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=E2=80=99t 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.

=E2=80=9Cpython updates=E2=80=9D even.  :-)

> 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.

I would prefer to restrict grafts to security fixes, primarily because
they have possibly surprising side effects on the UI.

Ludo=E2=80=99.