From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: Vivien Kraus <vivien@planete-kraus.eu>, 69778@debbugs.gnu.org
Cc: rg@raghavgururajan.name, maxim.cournoyer@gmail.com
Subject: [bug#69778] [PATCH gnome-team v2 0/2] Make the glibmm-2.76 variable public in (gnu packages glib)
Date: Thu, 14 Mar 2024 20:17:35 +0100 [thread overview]
Message-ID: <994478b7ed8d7434c10fe771645201bef70339ce.camel@gmail.com> (raw)
In-Reply-To: <cover.1710439598.git.vivien@planete-kraus.eu>
Am Donnerstag, dem 14.03.2024 um 19:06 +0100 schrieb Vivien Kraus:
> Dear Guix,
>
> Telegram-desktop wants to be built with glibmm@2.76. I originally
> added it to (gnu packages telegram), but in this revision, I add it
> to (gnu packages glib). What do you think?
I won't be able to build it on my machine, but assuming you tested it
LGTM.
next prev parent reply other threads:[~2024-03-14 19:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-13 16:45 [bug#69778] [PATCH gnome-team] gnu: telegram: Build with glibmm@2.76 Vivien Kraus via Guix-patches via
2024-03-13 21:59 ` Liliana Marie Prikler
2024-03-17 1:30 ` Maxim Cournoyer
2024-03-14 18:06 ` [bug#69778] [PATCH gnome-team v2 0/2] Make the glibmm-2.76 variable public in (gnu packages glib) Vivien Kraus via Guix-patches via
2024-03-13 16:45 ` [bug#69778] [PATCH gnome-team v2 2/2] gnu: telegram: Build with glibmm@2.76 Vivien Kraus via Guix-patches via
2024-03-14 17:29 ` [bug#69778] [PATCH gnome-team v2 1/2] gnu: Add glibmm-2.76 Vivien Kraus via Guix-patches via
2024-03-14 19:17 ` Liliana Marie Prikler [this message]
2024-03-16 11:04 ` [bug#69778] [PATCH gnome-team v2 0/2] Make the glibmm-2.76 variable public in (gnu packages glib) Christopher Baines
2024-03-17 1:31 ` Maxim Cournoyer
2024-03-17 7:29 ` Vivien Kraus via Guix-patches via
2024-03-17 8:30 ` Liliana Marie Prikler
2024-03-21 18:25 ` Vivien Kraus via Guix-patches via
2024-03-21 18:49 ` Liliana Marie Prikler
2024-03-21 19: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
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=994478b7ed8d7434c10fe771645201bef70339ce.camel@gmail.com \
--to=liliana.prikler@gmail.com \
--cc=69778@debbugs.gnu.org \
--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).