bug#26534: [PATCH] gnu: Update glib to 2.52.1.

bug#26534: [PATCH] gnu: Update glib to 2.52.1.

[Roel Janssen]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: 0001-gnu-Update-glib-to-2.52.1.patch --]
[-- Type: text/x-patch, Size: 1186 bytes --]

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


[-- Attachment #2: Type: text/plain, Size: 65 bytes --]

Dear Guix,

Is it OK to update glib?

Kind regards,
Roel Janssen

bug#26534: [PATCH] gnu: Update glib to 2.52.1.

[Marius Bakke]

[-- Attachment #1: Type: text/plain, Size: 1705 bytes --]

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

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

bug#26534: [PATCH] gnu: Update glib to 2.52.1.

[Roel Janssen]

Marius Bakke writes:

> 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

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?

Kind regards,
Roel Janssen

bug#26534: [PATCH] gnu: Update glib to 2.52.1.

[Marius Bakke]

[-- Attachment #1: Type: text/plain, Size: 2513 bytes --]

Roel Janssen <roel@gnu.org> writes:

> Marius Bakke writes:
>
>> 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
>
> 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 :)

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

bug#26534: [PATCH] gnu: Update glib to 2.52.1.

[Roel Janssen]

Marius Bakke writes:

> Roel Janssen <roel@gnu.org> writes:
>
>> Marius Bakke writes:
>>
>>> 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
>>
>> 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

bug#26534: [PATCH] gnu: Update glib to 2.52.1.

[Marius Bakke]

[-- Attachment #1: Type: text/plain, Size: 2869 bytes --]

Roel Janssen <roel@gnu.org> writes:

> Marius Bakke writes:
>
>> Roel Janssen <roel@gnu.org> writes:
>>
>>> Marius Bakke writes:
>>>
>>>> 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
>>>
>>> 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.

Oops, I meant "refresh -t gnome -u" here :)

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

bug#26534: [PATCH] gnu: Update glib to 2.52.1.

[Kei Kebreau]

[-- Attachment #1: Type: text/plain, Size: 3167 bytes --]

Roel Janssen <roel@gnu.org> writes:

> Marius Bakke writes:
>
>> Roel Janssen <roel@gnu.org> writes:
>>
>>> Marius Bakke writes:
>>>
>>>> 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
>>>
>>> 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

Hi Roel,

I'm looking at updating GNOME packages as well. When I tried building
the most recent version of Eye of GNOME, glib gave me two test
failures. Do you think these failures could be a result of glib
dependencies needing to be updated, or is this fixable on its own?

Thanks in advance,
Kei

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

bug#26534: [PATCH] gnu: Update glib to 2.52.1.

[Roel Janssen]

Kei Kebreau writes:

> Roel Janssen <roel@gnu.org> writes:
>
>> Marius Bakke writes:
>>
>>> Roel Janssen <roel@gnu.org> writes:
>>>
>>>> Marius Bakke writes:
>>>>
>>>>> 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
>>>>
>>>> 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
>
> Hi Roel,
>
> I'm looking at updating GNOME packages as well. When I tried building
> the most recent version of Eye of GNOME, glib gave me two test
> failures. Do you think these failures could be a result of glib
> dependencies needing to be updated, or is this fixable on its own?
>
> Thanks in advance,
> Kei

Hi Kei,

I don't know.  I did:
$ guix refresh -t gnome -u

Do you have the build output log for the failed GLib?

Kind regards,
Roel Janssen

bug#26534: [PATCH] gnu: Update glib to 2.52.1.

[Roel Janssen]

Kei Kebreau writes:

> Roel Janssen <roel@gnu.org> writes:
>
>> Marius Bakke writes:
>>
>>> Roel Janssen <roel@gnu.org> writes:
>>>
>>>> Marius Bakke writes:
>>>>
>>>>> 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
>>>>
>>>> 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
>
> Hi Roel,
>
> I'm looking at updating GNOME packages as well. When I tried building
> the most recent version of Eye of GNOME, glib gave me two test
> failures. Do you think these failures could be a result of glib
> dependencies needing to be updated, or is this fixable on its own?
>
> Thanks in advance,
> Kei

Dear Kei,

I think I have found what fixes the two failing tests.. I run the tests
in parallel.  When I disabled running them in parallel, two tests fail
related to 'gdbus'.

Kind regards,
Roel Janssen

bug#26534: [PATCH] gnu: Update glib to 2.52.1.

[Kei Kebreau]

[-- Attachment #1: Type: text/plain, Size: 3817 bytes --]

Roel Janssen <roel@gnu.org> writes:

> Kei Kebreau writes:
>
>> Roel Janssen <roel@gnu.org> writes:
>>
>>> Marius Bakke writes:
>>>
>>>> Roel Janssen <roel@gnu.org> writes:
>>>>
>>>>> Marius Bakke writes:
>>>>>
>>>>>> 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
>>>>>
>>>>> 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
>>
>> Hi Roel,
>>
>> I'm looking at updating GNOME packages as well. When I tried building
>> the most recent version of Eye of GNOME, glib gave me two test
>> failures. Do you think these failures could be a result of glib
>> dependencies needing to be updated, or is this fixable on its own?
>>
>> Thanks in advance,
>> Kei
>
> Dear Kei,
>
> I think I have found what fixes the two failing tests.. I run the tests
> in parallel.  When I disabled running them in parallel, two tests fail
> related to 'gdbus'.
>
> Kind regards,
> Roel Janssen

I have good news! Your original patch works when I upgrade dbus to its
latest version, 1.10.18. So now we just need to update dbus and get the
update merged into gnome-updates.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]

bug#26534: [PATCH] gnu: Update glib to 2.52.1.

[Marius Bakke]

[-- Attachment #1: Type: text/plain, Size: 1087 bytes --]

Kei Kebreau <kei@openmailbox.org> writes:

>>> Hi Roel,
>>>
>>> I'm looking at updating GNOME packages as well. When I tried building
>>> the most recent version of Eye of GNOME, glib gave me two test
>>> failures. Do you think these failures could be a result of glib
>>> dependencies needing to be updated, or is this fixable on its own?
>>>
>>> Thanks in advance,
>>> Kei
>>
>> Dear Kei,
>>
>> I think I have found what fixes the two failing tests.. I run the tests
>> in parallel.  When I disabled running them in parallel, two tests fail
>> related to 'gdbus'.
>>
>> Kind regards,
>> Roel Janssen
>
> I have good news! Your original patch works when I upgrade dbus to its
> latest version, 1.10.18. So now we just need to update dbus and get the
> update merged into gnome-updates.

If "glib" depends on a newer "dbus", I think it should be added in
'gnome-updates' as well. Otherwise it will have to wait until the next
'core-updates' cycle slated for end of next month.

Thanks for working on this! Let's try to start building this branch on
Hydra next week, how does that sound?

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

bug#26534: [PATCH] gnu: Update glib to 2.52.1.

[Kei Kebreau]

[-- Attachment #1: Type: text/plain, Size: 1375 bytes --]

Marius Bakke <mbakke@fastmail.com> writes:

> Kei Kebreau <kei@openmailbox.org> writes:
>
>>>> Hi Roel,
>>>>
>>>> I'm looking at updating GNOME packages as well. When I tried building
>>>> the most recent version of Eye of GNOME, glib gave me two test
>>>> failures. Do you think these failures could be a result of glib
>>>> dependencies needing to be updated, or is this fixable on its own?
>>>>
>>>> Thanks in advance,
>>>> Kei
>>>
>>> Dear Kei,
>>>
>>> I think I have found what fixes the two failing tests.. I run the tests
>>> in parallel.  When I disabled running them in parallel, two tests fail
>>> related to 'gdbus'.
>>>
>>> Kind regards,
>>> Roel Janssen
>>
>> I have good news! Your original patch works when I upgrade dbus to its
>> latest version, 1.10.18. So now we just need to update dbus and get the
>> update merged into gnome-updates.
>
> If "glib" depends on a newer "dbus", I think it should be added in
> 'gnome-updates' as well. Otherwise it will have to wait until the next
> 'core-updates' cycle slated for end of next month.
>
> Thanks for working on this! Let's try to start building this branch on
> Hydra next week, how does that sound?

Provided that the rest of the package upgrades go smoothly, this is a
good idea. If someone could review the dbus upgrade patch I submitted
to the guix-patches mailing list, I can push it to gnome-updates.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]

bug#26534: [PATCH] gnu: Update glib to 2.52.1.

[Roel Janssen]

Kei Kebreau writes:

> Marius Bakke <mbakke@fastmail.com> writes:
>
>> Kei Kebreau <kei@openmailbox.org> writes:
>>
>>>>> Hi Roel,
>>>>>
>>>>> I'm looking at updating GNOME packages as well. When I tried building
>>>>> the most recent version of Eye of GNOME, glib gave me two test
>>>>> failures. Do you think these failures could be a result of glib
>>>>> dependencies needing to be updated, or is this fixable on its own?
>>>>>
>>>>> Thanks in advance,
>>>>> Kei
>>>>
>>>> Dear Kei,
>>>>
>>>> I think I have found what fixes the two failing tests.. I run the tests
>>>> in parallel.  When I disabled running them in parallel, two tests fail
>>>> related to 'gdbus'.
>>>>
>>>> Kind regards,
>>>> Roel Janssen
>>>
>>> I have good news! Your original patch works when I upgrade dbus to its
>>> latest version, 1.10.18. So now we just need to update dbus and get the
>>> update merged into gnome-updates.
>>
>> If "glib" depends on a newer "dbus", I think it should be added in
>> 'gnome-updates' as well. Otherwise it will have to wait until the next
>> 'core-updates' cycle slated for end of next month.
>>
>> Thanks for working on this! Let's try to start building this branch on
>> Hydra next week, how does that sound?
>
> Provided that the rest of the package upgrades go smoothly, this is a
> good idea. If someone could review the dbus upgrade patch I submitted
> to the guix-patches mailing list, I can push it to gnome-updates.

I cannot seem to find the patch message you are referring to, or is it
from 10 Oct 2016, titled "Dbus update 1.10.12 for core-updates"?

Kind regards,
Roel Janssen

bug#26534: [PATCH] gnu: Update glib to 2.52.1.

[Kei Kebreau]

[-- Attachment #1: Type: text/plain, Size: 1880 bytes --]

Roel Janssen <roel@gnu.org> writes:

> Kei Kebreau writes:
>
>> Marius Bakke <mbakke@fastmail.com> writes:
>>
>>> Kei Kebreau <kei@openmailbox.org> writes:
>>>
>>>>>> Hi Roel,
>>>>>>
>>>>>> I'm looking at updating GNOME packages as well. When I tried building
>>>>>> the most recent version of Eye of GNOME, glib gave me two test
>>>>>> failures. Do you think these failures could be a result of glib
>>>>>> dependencies needing to be updated, or is this fixable on its own?
>>>>>>
>>>>>> Thanks in advance,
>>>>>> Kei
>>>>>
>>>>> Dear Kei,
>>>>>
>>>>> I think I have found what fixes the two failing tests.. I run the tests
>>>>> in parallel.  When I disabled running them in parallel, two tests fail
>>>>> related to 'gdbus'.
>>>>>
>>>>> Kind regards,
>>>>> Roel Janssen
>>>>
>>>> I have good news! Your original patch works when I upgrade dbus to its
>>>> latest version, 1.10.18. So now we just need to update dbus and get the
>>>> update merged into gnome-updates.
>>>
>>> If "glib" depends on a newer "dbus", I think it should be added in
>>> 'gnome-updates' as well. Otherwise it will have to wait until the next
>>> 'core-updates' cycle slated for end of next month.
>>>
>>> Thanks for working on this! Let's try to start building this branch on
>>> Hydra next week, how does that sound?
>>
>> Provided that the rest of the package upgrades go smoothly, this is a
>> good idea. If someone could review the dbus upgrade patch I submitted
>> to the guix-patches mailing list, I can push it to gnome-updates.
>
> I cannot seem to find the patch message you are referring to, or is it
> from 10 Oct 2016, titled "Dbus update 1.10.12 for core-updates"?
>
> Kind regards,
> Roel Janssen

It's bug #26683 (it might not have shown up so quickly, as I had just
sent it). FWIW, I'm just going to push it to gnome-updates since
it's okay with Marius. Thanks for debugging the tests.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]

bug#26534: [PATCH] gnu: Update glib to 2.52.1.

[Marius Bakke]

[-- Attachment #1: Type: text/plain, Size: 1892 bytes --]

Kei Kebreau <kei@openmailbox.org> writes:

> Marius Bakke <mbakke@fastmail.com> writes:
>
>> Kei Kebreau <kei@openmailbox.org> writes:
>>
>>>>> Hi Roel,
>>>>>
>>>>> I'm looking at updating GNOME packages as well. When I tried building
>>>>> the most recent version of Eye of GNOME, glib gave me two test
>>>>> failures. Do you think these failures could be a result of glib
>>>>> dependencies needing to be updated, or is this fixable on its own?
>>>>>
>>>>> Thanks in advance,
>>>>> Kei
>>>>
>>>> Dear Kei,
>>>>
>>>> I think I have found what fixes the two failing tests.. I run the tests
>>>> in parallel.  When I disabled running them in parallel, two tests fail
>>>> related to 'gdbus'.
>>>>
>>>> Kind regards,
>>>> Roel Janssen
>>>
>>> I have good news! Your original patch works when I upgrade dbus to its
>>> latest version, 1.10.18. So now we just need to update dbus and get the
>>> update merged into gnome-updates.
>>
>> If "glib" depends on a newer "dbus", I think it should be added in
>> 'gnome-updates' as well. Otherwise it will have to wait until the next
>> 'core-updates' cycle slated for end of next month.
>>
>> Thanks for working on this! Let's try to start building this branch on
>> Hydra next week, how does that sound?
>
> Provided that the rest of the package upgrades go smoothly, this is a
> good idea. If someone could review the dbus upgrade patch I submitted
> to the guix-patches mailing list, I can push it to gnome-updates.

I believe such simple updates are OK to just push, provided it builds
and you've verified the GPG signature and checked the code and changelog
for e.g. obsolete inputs or arguments (also see HACKING).

Obviously at 1500 dependents dbus can't be updated in 'master', but it's
okay for 'gnome-updates' since most of the dependent packages comes from
"glib" anyway:

https://lists.gnu.org/archive/html/guix-devel/2016-10/msg00933.html

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]