Roel Janssen <roel@gnu.org> writes:

> From 802c557c95ae9cbe7edeec1ab58fc05ef4c4cd32 Mon Sep 17 00:00:00 2001
> From: Roel Janssen <roel@gnu.org>
> 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