From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ricardo Wurmus Subject: Re: [PATCH 1/2] gnu: python-2: Update to 2.7.11 Date: Fri, 22 Apr 2016 08:52:32 +0200 Message-ID: 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> Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:50818) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1atUxL-000128-Qt for guix-devel@gnu.org; Fri, 22 Apr 2016 02:52:48 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1atUxI-0006nw-KZ for guix-devel@gnu.org; Fri, 22 Apr 2016 02:52:47 -0400 Received: from pegasus.bbbm.mdc-berlin.de ([141.80.25.20]:42241) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1atUxI-0006ns-BB for guix-devel@gnu.org; Fri, 22 Apr 2016 02:52:44 -0400 In-Reply-To: <5719C7EF.9090906@crazy-compilers.com> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Hartmut Goebel Cc: guix-devel@gnu.org Hartmut Goebel writes: > Am 21.04.2016 um 23:20 schrieb Efraim Flashner: >> This one is already updated in core-updates > > What is this "core-updates" thing? > > SCNR I assume this is a branch. But the manual is not wasting a single > word about branches in the repo. So how I am expected to know this. It=E2=80=99s a branch. It=E2=80=99s not in the manual because it=E2=80=99= s just an operational detail of how we use the build farm at hydra.gnu.org. > And why is a minor update in "core-updates" and not on the main-line? 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 separate branch for updates that cause a lot of rebuilds we can build substitutes in the background. Once most of the substitutes have been built we merge =E2=80=9Ccore-updates=E2=80=9D into =E2=80=9Cmaster=E2=80=9D= , so that people upgrading to latest master will be able to download substitutes. ~~ Ricardo