From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:57802) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1d0EuN-0006eu-CI for guix-patches@gnu.org; Mon, 17 Apr 2017 18:14:08 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1d0EuI-0002jW-D0 for guix-patches@gnu.org; Mon, 17 Apr 2017 18:14:07 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:54928) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1d0EuI-0002jQ-9C for guix-patches@gnu.org; Mon, 17 Apr 2017 18:14:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1d0EuI-0004P0-4L for guix-patches@gnu.org; Mon, 17 Apr 2017 18:14:02 -0400 Subject: bug#26534: [PATCH] gnu: Update glib to 2.52.1. Resent-Message-ID: References: <87a87ga233.fsf@gnu.org> <87vaq4kw2n.fsf@fastmail.com> <871ssr2o7x.fsf@gnu.org> <87fuh7knbv.fsf@fastmail.com> From: Roel Janssen In-reply-to: <87fuh7knbv.fsf@fastmail.com> Date: Tue, 18 Apr 2017 00:12:57 +0200 Message-ID: <87shl6r8d2.fsf@gnu.org> MIME-Version: 1.0 Content-Type: text/plain List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org Sender: "Guix-patches" To: Marius Bakke Cc: 26534@debbugs.gnu.org Marius Bakke writes: > Roel Janssen writes: > >> Marius Bakke writes: >> >>> Roel Janssen writes: >>> >>>> From 802c557c95ae9cbe7edeec1ab58fc05ef4c4cd32 Mon Sep 17 00:00:00 2001 >>>> From: Roel Janssen >>>> Date: Sun, 16 Apr 2017 15:53:54 +0200 >>>> Subject: [PATCH] gnu: Update glib to 2.52.1. >>>> >>>> * gnu/packages/glib.scm (glib): Update to 2.52.1. >>>> --- >>>> gnu/packages/glib.scm | 4 ++-- >>>> 1 file changed, 2 insertions(+), 2 deletions(-) >>>> >>>> diff --git a/gnu/packages/glib.scm b/gnu/packages/glib.scm >>>> index 6de9cce0b..4e29a550b 100644 >>>> --- a/gnu/packages/glib.scm >>>> +++ b/gnu/packages/glib.scm >>>> @@ -137,7 +137,7 @@ shared NFS home directories.") >>>> (define glib >>>> (package >>>> (name "glib") >>>> - (version "2.50.3") >>>> + (version "2.52.1") >>>> (source (origin >>>> (method url-fetch) >>>> (uri (string-append "mirror://gnome/sources/" >>>> @@ -145,7 +145,7 @@ shared NFS home directories.") >>>> name "-" version ".tar.xz")) >>>> (sha256 >>>> (base32 >>>> - "16frrwhc1yqkzx6bgh3060g94dr2biab17fb01mrni819jzr9vl2")) >>>> + "0vsqrvjwsk2x3mm2i428hpm5vgsi1b384l6xdhm7xmzj2yw2d34l")) >>>> (patches (search-patches "glib-tests-timer.patch")))) >>>> (build-system gnu-build-system) >>>> (outputs '("out" ; everything >>>> -- >>>> 2.12.1 >>>> >>>> Dear Guix, >>>> >>>> Is it OK to update glib? >>> >>> I suspect this would require some other GTK updates as well. Maybe we >>> can start a new "gnome-updates" branch[0] and try to bring everything up >>> to date. "glib" alone has almost 1500 dependent packages which is too >>> much for "staging". What do you think? >>> >>> [0] https://lists.gnu.org/archive/html/guix-devel/2016-10/msg00933.html >> >> This is a good idea. The ultimate purpose is to get the latest GNOME >> release in GNU Guix. I cannot carry this task entirely myself, if we >> would like to get it in before the next GNOME release.. ;) >> >> So, I am not sure we need to build everything on Hydra, since it's >> already under a high load. Maybe it's enough to create a branch in the >> Git repository and do the builds locally? > > I think pushing a "gnome-updates" branch to Savannah is a good start :) > `./pre-inst-env guix refresh -u gnome` appears able to do the grunt of > it. Let's start a Hydra evaluation once most packages are updated and > see how it goes :) I pushed the branch and put the glib update there. I will push of 'refresh -u gnome' there as well. Kind regards, Roel Janssen