[bug#69911] [PATCH gnome-team 1/6] gnu: folks: Update to 0.15.8.

[bug#69911] [PATCH gnome-team 1/6] gnu: folks: Update to 0.15.8.

[Vivien Kraus via Guix-patches via]

* gnu/packages/gnome.scm (folks): Update to 0.15.8.

Change-Id: I36ceb7d70e315a22352495e3470ce9fd7e126196
---
 gnu/packages/gnome.scm | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/gnu/packages/gnome.scm b/gnu/packages/gnome.scm
index 7e7d77a3a2..f82ca3e30a 100644
--- a/gnu/packages/gnome.scm
+++ b/gnu/packages/gnome.scm
@@ -10841,7 +10841,7 @@ (define-public gnome-shell-extensions
 (define-public folks
   (package
     (name "folks")
-    (version "0.15.7")
+    (version "0.15.8")
     (source (origin
               (method url-fetch)
               (uri (string-append
@@ -10850,7 +10850,7 @@ (define-public folks
                     "folks-" version ".tar.xz"))
               (sha256
                (base32
-                "0wbq6h7hv8048c2m554b385qp4i99svaxxp7balwl4ijysg223qj"))))
+                "1hj9brran2azy3scyf913svhxjrmya83fi7x239h33rp7vxnljlm"))))
     (build-system meson-build-system)
     (arguments
      '(#:phases
-- 
2.41.0

[bug#69911] [PATCH gnome-team 2/6] gnu: gnome-online-accounts: Update to 3.48.1.

[Vivien Kraus via Guix-patches via]

* gnu/packages/gnome.scm (gnome-online-accounts): Update to 3.48.1.

Change-Id: I779bc5ae3978b59489abd8c3c54944c035674fc6
---
 gnu/packages/gnome.scm | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/gnu/packages/gnome.scm b/gnu/packages/gnome.scm
index f82ca3e30a..f6a5c4088d 100644
--- a/gnu/packages/gnome.scm
+++ b/gnu/packages/gnome.scm
@@ -8096,7 +8096,7 @@ (define-public mutter
 (define-public gnome-online-accounts
   (package
     (name "gnome-online-accounts")
-    (version "3.48.0")
+    (version "3.48.1")
     (source (origin
               (method url-fetch)
               (uri (string-append "mirror://gnome/sources/" name "/"
@@ -8104,7 +8104,7 @@ (define-public gnome-online-accounts
                                   name "-" version ".tar.xz"))
               (sha256
                (base32
-                "1gvmc4k5vm4qd97yfkd5a4sixz0pfq9nblss42c2mmyvzzybk2s1"))))
+                "12kza6wss01kcka1zc2bck4hwgc55vzwwdxabk75qndzhh8cg81y"))))
     (build-system meson-build-system)
     (arguments
      (list
-- 
2.41.0

[bug#69911] [PATCH gnome-team 3/6] gnu: gnome-shell: Update to 44.10.

[Vivien Kraus via Guix-patches via]

* gnu/packages/gnome.scm (gnome-shell): Update to 44.10.

Change-Id: Ib4591ac6b34af33e63468eddd21015b823a6f8da
---
 gnu/packages/gnome.scm | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/gnu/packages/gnome.scm b/gnu/packages/gnome.scm
index f6a5c4088d..5432ebc27b 100644
--- a/gnu/packages/gnome.scm
+++ b/gnu/packages/gnome.scm
@@ -9284,7 +9284,7 @@ (define-public gnome-control-center
 (define-public gnome-shell
   (package
     (name "gnome-shell")
-    (version "44.9")
+    (version "44.10")
     (source (origin
               (method url-fetch)
               (uri (string-append "mirror://gnome/sources/" name "/"
@@ -9292,7 +9292,7 @@ (define-public gnome-shell
                                   name "-" version ".tar.xz"))
               (sha256
                (base32
-                "0k5pxbwwqi1fqpvja77xl0fv7y46gaz17p29f74wpzyb61g16rhp"))))
+                "01pw9qnnvh64x56z1gqh0qk6vfn0ihh4zijq23f4bpz9wszlbpwf"))))
     (build-system meson-build-system)
     (arguments
      (let ((disallowed-references
-- 
2.41.0

[bug#69911] [PATCH gnome-team 4/6] gnu: gtkmm@3: Update to 3.24.9.

[Vivien Kraus via Guix-patches via]

* gnu/packages/gtk.scm (gtkmm-3): Update to 3.24.9.

Change-Id: I63e4cf6d040ff7d147965d5320ab818ff553456b
---
 gnu/packages/gtk.scm | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/gnu/packages/gtk.scm b/gnu/packages/gtk.scm
index f43eece4f2..5062d3aeda 100644
--- a/gnu/packages/gtk.scm
+++ b/gnu/packages/gtk.scm
@@ -1878,7 +1878,7 @@ (define-public gtkmm-3
   (package
     (inherit gtkmm)
     (name "gtkmm")
-    (version "3.24.8")
+    (version "3.24.9")
     (source
      (origin
        (method url-fetch)
@@ -1887,7 +1887,7 @@ (define-public gtkmm-3
                        (version-major+minor version)  "/"
                        name "-" version ".tar.xz"))
        (sha256
-        (base32 "1i4ql0j6id6g34w5nbhd7vjak7l3s50lqgdjaj2ranrfj9j0r56j"))))
+        (base32 "1kj4mla3z9kxhdby5w88nl744xkmq6xchf79m1kfa72p0kjbzm9h"))))
     (propagated-inputs
      `(("atkmm-2.28" ,atkmm-2.28)
        ("cairomm-1.14" ,cairomm-1.14)
-- 
2.41.0

[bug#69911] [PATCH gnome-team 5/6] gnu: template-glib: Update to 3.36.2.

[Vivien Kraus via Guix-patches via]

* gnu/packages/glib.scm (template-glib): Update to 3.36.2.

Change-Id: Ib945eb6748143cb9b921758215ce00e721f288b0
---
 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 5848ebc7aa..bff8bec81f 100644
--- a/gnu/packages/glib.scm
+++ b/gnu/packages/glib.scm
@@ -1437,7 +1437,7 @@ (define perl-net-dbus-glib
 (define-public template-glib
   (package
     (name "template-glib")
-    (version "3.36.1")
+    (version "3.36.2")
     (source (origin
               (method url-fetch)
               (uri (string-append "mirror://gnome/sources/" name "/"
@@ -1445,7 +1445,7 @@ (define-public template-glib
                                   name "-" version ".tar.xz"))
               (sha256
                (base32
-                "00x5yq1yidxxv6hmlvblpp2k0vf60s0xzyi0psplbmss70bpl5iv"))))
+                "0j4rc4jvxk5pzmx5831s90m9g4cfyp10hxd1ndiyg34806jg6800"))))
     (build-system meson-build-system)
     (arguments
      (list #:configure-flags #~'("-D" "gtk_doc=true")))
-- 
2.41.0

[bug#69911] [PATCH gnome-team 6/6] gnu: vala: Update to 0.56.16.

[Vivien Kraus via Guix-patches via]

* gnu/packages/gnome.scm (vala): Update to 0.56.16.

Change-Id: Ia5c0c608642d4505efef52d882a51bb83c3dd539
---
 gnu/packages/gnome.scm | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/gnu/packages/gnome.scm b/gnu/packages/gnome.scm
index 5432ebc27b..b1709458b0 100644
--- a/gnu/packages/gnome.scm
+++ b/gnu/packages/gnome.scm
@@ -4487,7 +4487,7 @@ (define-public seahorse
 (define-public vala
   (package
     (name "vala")
-    (version "0.56.14")
+    (version "0.56.16")
     (source (origin
               (method url-fetch)
               (uri (string-append "mirror://gnome/sources/vala/"
@@ -4495,7 +4495,7 @@ (define-public vala
                                   "vala-" version ".tar.xz"))
               (sha256
                (base32
-                "0mzmldhf6474dp2jkxj160kkafdz32c2l5f8xnm05p4vr9lc50lk"))))
+                "16yaiff5nl2dfyvs3bj8y7wvzh9riz6wqlx7csgg1lpm01b7nj05"))))
     (build-system glib-or-gtk-build-system)
     (arguments
      (list
-- 
2.41.0

[bug#69911] [PATCH gnome-team 0/6] GNOME 44.10 update

[Vivien Kraus via Guix-patches via]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 619 bytes --]

Dear Guix,

GNOME 44.10 is out. I could not test it, because I don’t have enough disk
space for the world rebuild.

Best regards,

Vivien

Vivien Kraus (6):
  gnu: folks: Update to 0.15.8.
  gnu: gnome-online-accounts: Update to 3.48.1.
  gnu: gnome-shell: Update to 44.10.
  gnu: gtkmm@3: Update to 3.24.9.
  gnu: template-glib: Update to 3.36.2.
  gnu: vala: Update to 0.56.16.

 gnu/packages/glib.scm  |  4 ++--
 gnu/packages/gnome.scm | 16 ++++++++--------
 gnu/packages/gtk.scm   |  4 ++--
 3 files changed, 12 insertions(+), 12 deletions(-)


base-commit: 1caa0eeee5042f33bc0bb66dc38bed7513cad0fb
-- 
2.41.0

[bug#69414] [bug#69911] [PATCH gnome-team 0/6] GNOME 44.10 update

[Christopher Baines]

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


Vivien Kraus via Guix-patches via <guix-patches@gnu.org> writes:

> Dear Guix,
>
> GNOME 44.10 is out. I could not test it, because I don’t have enough disk
> space for the world rebuild.

I picked all but the vala and gtkmm@3 update (as those both have lots of
dependents), applied them to gnome-team and things seem to build
fine. I've also reconfigured to gnome-team and haven't come across any
problems yet. I've now pushed those patches to gnome-team.

I don't know much about the substance of the changes on gnome-team, but
the substitute availability is looking good at least (it's just
i686-linux that's lagging behind on bordeaux).

I'll close this issue but feel free to re-send the vala and gtkmm@3
updates to a new issue.

Is there anything that needs to happen before gnome-team can be merged?

Thanks,

Chris

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

[bug#69911] [PATCH gnome-team 0/6] GNOME 44.10 update

[Vivien Kraus via Guix-patches via]

Hello,

Le mercredi 20 mars 2024 à 10:42 +0000, Christopher Baines a écrit :
> Is there anything that needs to happen before gnome-team can be
> merged?

There are concerning failures, such as lightdm, that must be
investigated. QA has also highlighted flaky tests in a bunch of
packages, and a time-bomb (kcalendarcore).

I will resubmit the world-rebuilding patches in a new issue.

Best regards,

Vivien

[bug#69414] [bug#69911] [PATCH gnome-team 0/6] GNOME 44.10 update

[Christopher Baines]

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


Vivien Kraus <vivien@planete-kraus.eu> writes:

> Hello,
>
> Le mercredi 20 mars 2024 à 10:42 +0000, Christopher Baines a écrit :
>> Is there anything that needs to happen before gnome-team can be
>> merged?
>
> There are concerning failures, such as lightdm, that must be
> investigated. QA has also highlighted flaky tests in a bunch of
> packages, and a time-bomb (kcalendarcore).

I had a go to looking in to lightdm not building and it looks to maybe
be dbus related, but I've got no idea really. Debian and nixpkgs don't
even run the test suite as far as I can tell. I also tried the system
test and that seems to pass. So maybe we raise the issue with upstream
and disable the testsuite for now.

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

[bug#69414] [bug#69911] [PATCH gnome-team 0/6] GNOME 44.10 update

[Maxim Cournoyer]

Hi Christopher,

Christopher Baines <mail@cbaines.net> writes:

> Vivien Kraus <vivien@planete-kraus.eu> writes:
>
>> Hello,
>>
>> Le mercredi 20 mars 2024 à 10:42 +0000, Christopher Baines a écrit :
>>> Is there anything that needs to happen before gnome-team can be
>>> merged?
>>
>> There are concerning failures, such as lightdm, that must be
>> investigated. QA has also highlighted flaky tests in a bunch of
>> packages, and a time-bomb (kcalendarcore).
>
> I had a go to looking in to lightdm not building and it looks to maybe
> be dbus related, but I've got no idea really. Debian and nixpkgs don't
> even run the test suite as far as I can tell. I also tried the system
> test and that seems to pass. So maybe we raise the issue with upstream
> and disable the testsuite for now.

I'd rather we spend a bit of time investigating the underlying failure
and engage with upstream if there's a need.  Setting #:tests? #f is
easy, but it means the sometimes serious efforts that were needed to
enable the test suite go into bitrot, making it harder to re-enable at
a later time (thus unlikely).

-- 
Thanks,
Maxim

[bug#69414] [bug#69911] [PATCH gnome-team 0/6] GNOME 44.10 update

[Christopher Baines]

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


Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:

> Hi Christopher,
>
> Christopher Baines <mail@cbaines.net> writes:
>
>> Vivien Kraus <vivien@planete-kraus.eu> writes:
>>
>>> Hello,
>>>
>>> Le mercredi 20 mars 2024 à 10:42 +0000, Christopher Baines a écrit :
>>>> Is there anything that needs to happen before gnome-team can be
>>>> merged?
>>>
>>> There are concerning failures, such as lightdm, that must be
>>> investigated. QA has also highlighted flaky tests in a bunch of
>>> packages, and a time-bomb (kcalendarcore).
>>
>> I had a go to looking in to lightdm not building and it looks to maybe
>> be dbus related, but I've got no idea really. Debian and nixpkgs don't
>> even run the test suite as far as I can tell. I also tried the system
>> test and that seems to pass. So maybe we raise the issue with upstream
>> and disable the testsuite for now.
>
> I'd rather we spend a bit of time investigating the underlying failure
> and engage with upstream if there's a need.  Setting #:tests? #f is
> easy, but it means the sometimes serious efforts that were needed to
> enable the test suite go into bitrot, making it harder to re-enable at
> a later time (thus unlikely).

To elaborate on the point I'm trying to make, having spent a bit of time
looking in to this specific issue, I don't think it's worth blocking the
gnome-team merge over an issue with running the lightdm testsuite.

Obviously if there's actually an issue with lightdm, then that's
different. This is also somewhat personal since I've got almost no
knowledge about lightdm or the dbus problems I suspect might be related.

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

[bug#69414] [bug#69911] [PATCH gnome-team 0/6] GNOME 44.10 update

[Christopher Baines]

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


Christopher Baines <mail@cbaines.net> writes:

> Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:
>
>> Hi Christopher,
>>
>> Christopher Baines <mail@cbaines.net> writes:
>>
>>> Vivien Kraus <vivien@planete-kraus.eu> writes:
>>>
>>>> Hello,
>>>>
>>>> Le mercredi 20 mars 2024 à 10:42 +0000, Christopher Baines a écrit :
>>>>> Is there anything that needs to happen before gnome-team can be
>>>>> merged?
>>>>
>>>> There are concerning failures, such as lightdm, that must be
>>>> investigated. QA has also highlighted flaky tests in a bunch of
>>>> packages, and a time-bomb (kcalendarcore).
>>>
>>> I had a go to looking in to lightdm not building and it looks to maybe
>>> be dbus related, but I've got no idea really. Debian and nixpkgs don't
>>> even run the test suite as far as I can tell. I also tried the system
>>> test and that seems to pass. So maybe we raise the issue with upstream
>>> and disable the testsuite for now.
>>
>> I'd rather we spend a bit of time investigating the underlying failure
>> and engage with upstream if there's a need.  Setting #:tests? #f is
>> easy, but it means the sometimes serious efforts that were needed to
>> enable the test suite go into bitrot, making it harder to re-enable at
>> a later time (thus unlikely).
>
> To elaborate on the point I'm trying to make, having spent a bit of time
> looking in to this specific issue, I don't think it's worth blocking the
> gnome-team merge over an issue with running the lightdm testsuite.
>
> Obviously if there's actually an issue with lightdm, then that's
> different. This is also somewhat personal since I've got almost no
> knowledge about lightdm or the dbus problems I suspect might be related.

Thanks to Vivian's patch (#69948) we're now building lightdm with an
older dbus.

I had a look for failures in QA and I didn't really see
anything. There's some issue with the tests for gtk on aarch64-linux,
not sure what's going on there, but I don't think that blocks merging.

Is there anything that needs to happen before gnome-team can be merged?

Thanks,

Chris

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

[bug#69414] [bug#69911] [PATCH gnome-team 0/6] GNOME 44.10 update

[Liliana Marie Prikler]

Am Mittwoch, dem 27.03.2024 um 12:23 +0000 schrieb Christopher Baines:
> 
> Christopher Baines <mail@cbaines.net> writes:
> 
> > Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:
> > 
> > > Hi Christopher,
> > > 
> > > Christopher Baines <mail@cbaines.net> writes:
> > > 
> > > > Vivien Kraus <vivien@planete-kraus.eu> writes:
> > > > 
> > > > > Hello,
> > > > > 
> > > > > Le mercredi 20 mars 2024 à 10:42 +0000, Christopher Baines a
> > > > > écrit :
> > > > > > Is there anything that needs to happen before gnome-team
> > > > > > can be
> > > > > > merged?
> > > > > 
> > > > > There are concerning failures, such as lightdm, that must be
> > > > > investigated. QA has also highlighted flaky tests in a bunch
> > > > > of
> > > > > packages, and a time-bomb (kcalendarcore).
> > > > 
> > > > I had a go to looking in to lightdm not building and it looks
> > > > to maybe
> > > > be dbus related, but I've got no idea really. Debian and
> > > > nixpkgs don't
> > > > even run the test suite as far as I can tell. I also tried the
> > > > system
> > > > test and that seems to pass. So maybe we raise the issue with
> > > > upstream
> > > > and disable the testsuite for now.
> > > 
> > > I'd rather we spend a bit of time investigating the underlying
> > > failure
> > > and engage with upstream if there's a need.  Setting #:tests? #f
> > > is
> > > easy, but it means the sometimes serious efforts that were needed
> > > to
> > > enable the test suite go into bitrot, making it harder to re-
> > > enable at
> > > a later time (thus unlikely).
> > 
> > To elaborate on the point I'm trying to make, having spent a bit of
> > time
> > looking in to this specific issue, I don't think it's worth
> > blocking the
> > gnome-team merge over an issue with running the lightdm testsuite.
> > 
> > Obviously if there's actually an issue with lightdm, then that's
> > different. This is also somewhat personal since I've got almost no
> > knowledge about lightdm or the dbus problems I suspect might be
> > related.
> 
> Thanks to Vivian's patch (#69948) we're now building lightdm with an
> older dbus.
> 
> I had a look for failures in QA and I didn't really see
> anything. There's some issue with the tests for gtk on aarch64-linux,
> not sure what's going on there, but I don't think that blocks
> merging.
> 
> Is there anything that needs to happen before gnome-team can be
> merged?
QA also LGTM, let's get this merged.