GNU bug report logs - #26534
[PATCH] gnu: Update glib to 2.52.1.

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 26534 in the body.
You can then email your comments to 26534 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Roel Janssen <roel <at> gnu.org>
To: guix-patches <at> gnu.org
Subject: [PATCH] gnu: Update glib to 2.52.1.
Date: Sun, 16 Apr 2017 15:56:00 +0200

[0001-gnu-Update-glib-to-2.52.1.patch (text/x-patch, attachment)]

[Message part 2 (text/plain, inline)]

Dear Guix,

Is it OK to update glib?

Kind regards,
Roel Janssen

Message #8 received at 26534 <at> debbugs.gnu.org (full text, mbox):

From: Marius Bakke <mbakke <at> fastmail.com>
To: Roel Janssen <roel <at> gnu.org>, 26534 <at> debbugs.gnu.org
Subject: Re: bug#26534: [PATCH] gnu: Update glib to 2.52.1.
Date: Sun, 16 Apr 2017 21:10:24 +0200

[Message part 1 (text/plain, inline)]

Roel Janssen <roel <at> gnu.org> writes:

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

[signature.asc (application/pgp-signature, inline)]

Message #11 received at 26534 <at> debbugs.gnu.org (full text, mbox):

From: Roel Janssen <roel <at> gnu.org>
To: Marius Bakke <mbakke <at> fastmail.com>
Cc: 26534 <at> debbugs.gnu.org
Subject: Re: bug#26534: [PATCH] gnu: Update glib to 2.52.1.
Date: Mon, 17 Apr 2017 14:49:38 +0200

Marius Bakke writes:

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

Message #14 received at 26534 <at> debbugs.gnu.org (full text, mbox):

From: Marius Bakke <mbakke <at> fastmail.com>
To: Roel Janssen <roel <at> gnu.org>
Cc: 26534 <at> debbugs.gnu.org
Subject: Re: bug#26534: [PATCH] gnu: Update glib to 2.52.1.
Date: Mon, 17 Apr 2017 18:31:32 +0200

[Message part 1 (text/plain, inline)]

Roel Janssen <roel <at> gnu.org> writes:

> Marius Bakke writes:
>
>> Roel Janssen <roel <at> gnu.org> writes:
>>
>>> From 802c557c95ae9cbe7edeec1ab58fc05ef4c4cd32 Mon Sep 17 00:00:00 2001
>>> From: Roel Janssen <roel <at> 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 :)

[signature.asc (application/pgp-signature, inline)]

Message #17 received at 26534 <at> debbugs.gnu.org (full text, mbox):

From: Roel Janssen <roel <at> gnu.org>
To: Marius Bakke <mbakke <at> fastmail.com>
Cc: 26534 <at> debbugs.gnu.org
Subject: Re: bug#26534: [PATCH] gnu: Update glib to 2.52.1.
Date: Tue, 18 Apr 2017 00:12:57 +0200

Marius Bakke writes:

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

Message #20 received at 26534 <at> debbugs.gnu.org (full text, mbox):

From: Marius Bakke <mbakke <at> fastmail.com>
To: Roel Janssen <roel <at> gnu.org>
Cc: 26534 <at> debbugs.gnu.org
Subject: Re: bug#26534: [PATCH] gnu: Update glib to 2.52.1.
Date: Tue, 18 Apr 2017 00:19:34 +0200

[Message part 1 (text/plain, inline)]

Roel Janssen <roel <at> gnu.org> writes:

> Marius Bakke writes:
>
>> Roel Janssen <roel <at> gnu.org> writes:
>>
>>> Marius Bakke writes:
>>>
>>>> Roel Janssen <roel <at> gnu.org> writes:
>>>>
>>>>> From 802c557c95ae9cbe7edeec1ab58fc05ef4c4cd32 Mon Sep 17 00:00:00 2001
>>>>> From: Roel Janssen <roel <at> 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 :)

[signature.asc (application/pgp-signature, inline)]

Message #23 received at 26534 <at> debbugs.gnu.org (full text, mbox):

From: Kei Kebreau <kei <at> openmailbox.org>
To: Roel Janssen <roel <at> gnu.org>
Cc: Marius Bakke <mbakke <at> fastmail.com>, 26534 <at> debbugs.gnu.org
Subject: Re: bug#26534: [PATCH] gnu: Update glib to 2.52.1.
Date: Sun, 23 Apr 2017 13:44:39 -0400

[Message part 1 (text/plain, inline)]

Roel Janssen <roel <at> gnu.org> writes:

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

[signature.asc (application/pgp-signature, inline)]

Message #26 received at 26534 <at> debbugs.gnu.org (full text, mbox):

From: Roel Janssen <roel <at> gnu.org>
To: Kei Kebreau <kei <at> openmailbox.org>
Cc: Marius Bakke <mbakke <at> fastmail.com>, 26534 <at> debbugs.gnu.org
Subject: Re: bug#26534: [PATCH] gnu: Update glib to 2.52.1.
Date: Mon, 24 Apr 2017 14:05:59 +0200

Kei Kebreau writes:

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

Message #29 received at 26534 <at> debbugs.gnu.org (full text, mbox):

From: Roel Janssen <roel <at> gnu.org>
To: Kei Kebreau <kei <at> openmailbox.org>
Cc: Marius Bakke <mbakke <at> fastmail.com>, 26534 <at> debbugs.gnu.org
Subject: Re: bug#26534: [PATCH] gnu: Update glib to 2.52.1.
Date: Mon, 24 Apr 2017 21:21:42 +0200

Kei Kebreau writes:

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

Message #32 received at 26534 <at> debbugs.gnu.org (full text, mbox):

From: Kei Kebreau <kei <at> openmailbox.org>
To: Roel Janssen <roel <at> gnu.org>
Cc: Marius Bakke <mbakke <at> fastmail.com>, 26534 <at> debbugs.gnu.org
Subject: Re: bug#26534: [PATCH] gnu: Update glib to 2.52.1.
Date: Thu, 27 Apr 2017 13:35:41 -0400

[Message part 1 (text/plain, inline)]

Roel Janssen <roel <at> gnu.org> writes:

> Kei Kebreau writes:
>
>> Roel Janssen <roel <at> gnu.org> writes:
>>
>>> Marius Bakke writes:
>>>
>>>> Roel Janssen <roel <at> gnu.org> writes:
>>>>
>>>>> Marius Bakke writes:
>>>>>
>>>>>> Roel Janssen <roel <at> gnu.org> writes:
>>>>>>
>>>>>>> From 802c557c95ae9cbe7edeec1ab58fc05ef4c4cd32 Mon Sep 17 00:00:00 2001
>>>>>>> From: Roel Janssen <roel <at> 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.

[signature.asc (application/pgp-signature, inline)]

Message #35 received at 26534 <at> debbugs.gnu.org (full text, mbox):

From: Marius Bakke <mbakke <at> fastmail.com>
To: Kei Kebreau <kei <at> openmailbox.org>, Roel Janssen <roel <at> gnu.org>
Cc: 26534 <at> debbugs.gnu.org
Subject: Re: bug#26534: [PATCH] gnu: Update glib to 2.52.1.
Date: Thu, 27 Apr 2017 19:50:18 +0200

[Message part 1 (text/plain, inline)]

Kei Kebreau <kei <at> 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?

[signature.asc (application/pgp-signature, inline)]

Message #38 received at 26534 <at> debbugs.gnu.org (full text, mbox):

From: Kei Kebreau <kei <at> openmailbox.org>
To: Marius Bakke <mbakke <at> fastmail.com>
Cc: Roel Janssen <roel <at> gnu.org>, 26534 <at> debbugs.gnu.org
Subject: Re: bug#26534: [PATCH] gnu: Update glib to 2.52.1.
Date: Thu, 27 Apr 2017 16:26:53 -0400

[Message part 1 (text/plain, inline)]

Marius Bakke <mbakke <at> fastmail.com> writes:

> Kei Kebreau <kei <at> 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.

[signature.asc (application/pgp-signature, inline)]

Message #41 received at 26534 <at> debbugs.gnu.org (full text, mbox):

From: Roel Janssen <roel <at> gnu.org>
To: Kei Kebreau <kei <at> openmailbox.org>
Cc: Marius Bakke <mbakke <at> fastmail.com>, 26534 <at> debbugs.gnu.org
Subject: Re: bug#26534: [PATCH] gnu: Update glib to 2.52.1.
Date: Fri, 28 Apr 2017 12:36:47 +0200

Kei Kebreau writes:

> Marius Bakke <mbakke <at> fastmail.com> writes:
>
>> Kei Kebreau <kei <at> 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

Message #44 received at 26534 <at> debbugs.gnu.org (full text, mbox):

From: Marius Bakke <mbakke <at> fastmail.com>
To: Kei Kebreau <kei <at> openmailbox.org>
Cc: Roel Janssen <roel <at> gnu.org>, 26534 <at> debbugs.gnu.org
Subject: Re: bug#26534: [PATCH] gnu: Update glib to 2.52.1.
Date: Fri, 28 Apr 2017 16:21:06 +0200

[Message part 1 (text/plain, inline)]

Kei Kebreau <kei <at> openmailbox.org> writes:

> Marius Bakke <mbakke <at> fastmail.com> writes:
>
>> Kei Kebreau <kei <at> 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

[signature.asc (application/pgp-signature, inline)]

Message #47 received at 26534 <at> debbugs.gnu.org (full text, mbox):

From: Kei Kebreau <kei <at> openmailbox.org>
To: Roel Janssen <roel <at> gnu.org>
Cc: Marius Bakke <mbakke <at> fastmail.com>, 26534 <at> debbugs.gnu.org
Subject: Re: bug#26534: [PATCH] gnu: Update glib to 2.52.1.
Date: Fri, 28 Apr 2017 11:44:21 -0400

[Message part 1 (text/plain, inline)]

Roel Janssen <roel <at> gnu.org> writes:

> Kei Kebreau writes:
>
>> Marius Bakke <mbakke <at> fastmail.com> writes:
>>
>>> Kei Kebreau <kei <at> 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.

[signature.asc (application/pgp-signature, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.