From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: "Zhu Zihao" <all_but_last@163.com>, "Ludovic Courtès" <ludo@gnu.org>
Cc: 54261@debbugs.gnu.org, Maxime Devos <maximedevos@telenet.be>
Subject: [bug#54261] [PATCH]: Update GTK to 4.6.1.
Date: Sun, 27 Mar 2022 09:38:24 +0200 [thread overview]
Message-ID: <f64f6ccfee268e806b067c30a4e298bebef8c6ec.camel@gmail.com> (raw)
In-Reply-To: <86bkxsjdso.fsf@163.com>
Am Sonntag, dem 27.03.2022 um 11:04 +0800 schrieb Zhu Zihao:
>
> ping. Any thoughts?
>
As far as I can see, the main issue (GTK propagating pango-next) has
not been addressed, we're just piling on workarounds. This is not the
way to go, as it will inevitably lead to more conflicts later on.
If possible, I'd suggest trying to build GTK against the old pango,
perhaps with a patch that can be removed on core-updates. WDYT?
next prev parent reply other threads:[~2022-03-27 7:39 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-05 15:00 [bug#54261] [PATCH]: Update GTK to 4.6.1 Zhu Zihao
[not found] ` <handler.54261.B.164649346324787.ack@debbugs.gnu.org>
2022-03-05 15:55 ` [bug#54261] Acknowledgement ([PATCH]: Update GTK to 4.6.1.) Zhu Zihao
2022-03-11 15:15 ` Zhu Zihao
2022-03-11 15:59 ` Maxime Devos
2022-03-11 16:01 ` Maxime Devos
2022-03-12 2:38 ` Zhu Zihao
2022-03-12 9:17 ` Maxime Devos
2022-03-12 9:32 ` Maxime Devos
2022-03-12 9:40 ` Maxime Devos
2022-03-12 16:06 ` Different package version in same environment was: " Zhu Zihao
2022-03-13 14:55 ` Maxime Devos
2022-03-11 16:03 ` Maxime Devos
2022-03-15 15:42 ` Zhu Zihao
2022-03-18 22:48 ` [bug#54261] [PATCH]: Update GTK to 4.6.1 Ludovic Courtès
2022-03-19 3:00 ` Zhu Zihao
2022-03-21 1:17 ` Zhu Zihao
2022-03-27 3:04 ` Zhu Zihao
2022-03-27 7:38 ` Liliana Marie Prikler [this message]
2022-03-28 15:37 ` Zhu Zihao
2022-03-28 18:19 ` Liliana Marie Prikler
2022-03-29 5:56 ` Zhu Zihao
2022-03-29 6:01 ` Zhu Zihao
2022-03-30 19:56 ` Ludovic Courtès
2022-03-31 5:13 ` Zhu Zihao
2022-03-29 13:34 ` Ludovic Courtès
2022-03-30 3:45 ` Zhu Zihao
2022-04-01 15:54 ` Ludovic Courtès
2022-04-02 3:41 ` Zhu Zihao
2022-04-04 20:12 ` bug#54261: " Ludovic Courtès
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=f64f6ccfee268e806b067c30a4e298bebef8c6ec.camel@gmail.com \
--to=liliana.prikler@gmail.com \
--cc=54261@debbugs.gnu.org \
--cc=all_but_last@163.com \
--cc=ludo@gnu.org \
--cc=maximedevos@telenet.be \
/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.