From: Vivien Kraus via Guix-patches via <guix-patches@gnu.org>
To: Christopher Baines <mail@cbaines.net>
Cc: maxim.cournoyer@gmail.com, 69414@debbugs.gnu.org,
liliana.prikler@gmail.com, rg@raghavgururajan.name,
69911-done@debbugs.gnu.org, 69911@debbugs.gnu.org
Subject: [bug#69911] [PATCH gnome-team 0/6] GNOME 44.10 update
Date: Wed, 20 Mar 2024 13:25:01 +0100 [thread overview]
Message-ID: <1631dd6cefebcfda0c8bd76d0f054e34e1c6dbc6.camel@planete-kraus.eu> (raw)
In-Reply-To: <875xxhkwju.fsf@cbaines.net>
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
next prev parent reply other threads:[~2024-03-20 12:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-20 6:30 [bug#69911] [PATCH gnome-team 0/6] GNOME 44.10 update Vivien Kraus via Guix-patches via
2024-03-18 19:26 ` [bug#69911] [PATCH gnome-team 1/6] gnu: folks: Update to 0.15.8 Vivien Kraus via Guix-patches via
2024-03-18 19:28 ` [bug#69911] [PATCH gnome-team 2/6] gnu: gnome-online-accounts: Update to 3.48.1 Vivien Kraus via Guix-patches via
2024-03-18 19:29 ` [bug#69911] [PATCH gnome-team 3/6] gnu: gnome-shell: Update to 44.10 Vivien Kraus via Guix-patches via
2024-03-18 19:30 ` [bug#69911] [PATCH gnome-team 4/6] gnu: gtkmm@3: Update to 3.24.9 Vivien Kraus via Guix-patches via
2024-03-18 19:34 ` [bug#69911] [PATCH gnome-team 5/6] gnu: template-glib: Update to 3.36.2 Vivien Kraus via Guix-patches via
2024-03-18 19:35 ` [bug#69911] [PATCH gnome-team 6/6] gnu: vala: Update to 0.56.16 Vivien Kraus via Guix-patches via
2024-03-20 10:42 ` [bug#69414] [bug#69911] [PATCH gnome-team 0/6] GNOME 44.10 update Christopher Baines
2024-03-20 12:25 ` Vivien Kraus via Guix-patches via [this message]
2024-03-20 13:58 ` Christopher Baines
2024-03-20 18:29 ` Maxim Cournoyer
2024-03-21 15:23 ` Christopher Baines
2024-03-27 12:23 ` Christopher Baines
2024-03-27 17:53 ` Liliana Marie Prikler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1631dd6cefebcfda0c8bd76d0f054e34e1c6dbc6.camel@planete-kraus.eu \
--to=guix-patches@gnu.org \
--cc=69414@debbugs.gnu.org \
--cc=69911-done@debbugs.gnu.org \
--cc=69911@debbugs.gnu.org \
--cc=liliana.prikler@gmail.com \
--cc=mail@cbaines.net \
--cc=maxim.cournoyer@gmail.com \
--cc=rg@raghavgururajan.name \
--cc=vivien@planete-kraus.eu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).