From: Vivien Kraus via Guix-patches via <guix-patches@gnu.org>
To: Liliana Marie Prikler <liliana.prikler@gmail.com>,
Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: 69778@debbugs.gnu.org, rg@raghavgururajan.name
Subject: [bug#69778] [PATCH gnome-team v2 0/2] Make the glibmm-2.76 variable public in (gnu packages glib)
Date: Thu, 21 Mar 2024 20:51:15 +0100 [thread overview]
Message-ID: <d8991ccd997c5c4ef1f520d7f2cc08f29c627d1c.camel@planete-kraus.eu> (raw)
In-Reply-To: <3765d971301b03c849d67597b6c000942d480b0e.camel@gmail.com>
Le jeudi 21 mars 2024 à 19:49 +0100, Liliana Marie Prikler a écrit :
> > https://github.com/desktop-app/lib_base/pull/186
> Hmm, could we still use that patch and make it "Fix build with
> glibmm-
> 2.78"
>
> From a cursory glance, it looks like some type signatures might have
> changed, but that's a guess.
I tried to find a combination of patches to backport, but it does not
work very well (this patch ignores other things that were changed
earlier, but that we would need to backport). It’s also not possible to
point lib_base to this exact commit, because it is too recent for other
parts of telegram.
This is not great but hopefully a full upgrade of telegram will fix
everything.
prev parent reply other threads:[~2024-03-21 19:52 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 ` [bug#69778] [PATCH gnome-team v2 0/2] Make the glibmm-2.76 variable public in (gnu packages glib) Liliana Marie Prikler
2024-03-16 11:04 ` 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 [this message]
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=d8991ccd997c5c4ef1f520d7f2cc08f29c627d1c.camel@planete-kraus.eu \
--to=guix-patches@gnu.org \
--cc=69778@debbugs.gnu.org \
--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 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).