From: Vivien Kraus via Guix-patches via <guix-patches@gnu.org>
To: 69256@debbugs.gnu.org, John Kehayias <john.kehayias@protonmail.com>
Cc: rg@raghavgururajan.name, Vivien Kraus <vivien@planete-kraus.eu>,
liliana.prikler@gmail.com, maxim.cournoyer@gmail.com
Subject: [bug#69256] [PATCH gnome-team] gnu: glibmm-2.64: Rename and update to 2.66.6.
Date: Wed, 21 Feb 2024 23:09:57 +0100 [thread overview]
Message-ID: <393810b59d5cb02196860e84f757ad7880a94c3a.camel@planete-kraus.eu> (raw)
In-Reply-To: <69d4f39a7273cc40db4daa836e8a4d77007828c3.1708287721.git.john.kehayias@protonmail.com>
Hello John!
This update looks good to me, save for eiciel. This package has had a
new release, 0.10.0, that claims to support gtk4. Could you update it
also? This would make the old glibmm-2.66 useless.
The other packages that you directly touch build fine on my machine.
Best regards,
Vivien
next prev parent reply other threads:[~2024-02-21 22:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-18 20:30 [bug#69256] [PATCH gnome-team] gnu: glibmm-2.64: Rename and update to 2.66.6 John Kehayias via Guix-patches via
2024-02-21 22:04 ` [bug#69256] [PATCH gnome-team v2 0/2] Building your glibmm update Vivien Kraus via Guix-patches via
2024-02-18 20:30 ` [bug#69256] [PATCH gnome-team v2 1/2] gnu: glibmm-2.64: Rename and update to 2.66.6 John Kehayias via Guix-patches via
2024-02-21 21:47 ` [bug#69256] [PATCH gnome-team v2 2/2] gnu: eiciel: Update to 0.10.0 Vivien Kraus via Guix-patches via
2024-02-24 6:31 ` bug#69256: [PATCH gnome-team v2 0/2] Building your glibmm update Liliana Marie Prikler
2024-02-21 22:09 ` Vivien Kraus via Guix-patches via [this message]
2024-02-22 5:25 ` [bug#69256] [PATCH gnome-team] gnu: glibmm-2.64: Rename and update to 2.66.6 Liliana Marie Prikler
2024-02-22 5:43 ` Vivien Kraus via Guix-patches via
2024-02-22 5:51 ` Vivien Kraus via Guix-patches via
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=393810b59d5cb02196860e84f757ad7880a94c3a.camel@planete-kraus.eu \
--to=guix-patches@gnu.org \
--cc=69256@debbugs.gnu.org \
--cc=john.kehayias@protonmail.com \
--cc=liliana.prikler@gmail.com \
--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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.