From: "Ludovic Courtès" <ludo@gnu.org>
To: Zhu Zihao <all_but_last@163.com>
Cc: 54261@debbugs.gnu.org, Maxime Devos <maximedevos@telenet.be>
Subject: [bug#54261] [PATCH]: Update GTK to 4.6.1.
Date: Fri, 18 Mar 2022 23:48:05 +0100 [thread overview]
Message-ID: <87y216op22.fsf_-_@gnu.org> (raw)
In-Reply-To: <8635jjfcgz.fsf@163.com> (Zhu Zihao's message of "Tue, 15 Mar 2022 23:42:37 +0800")
Hi,
The patches all LGTM, but unfortunately they break fcitx5-gtk, which
pulls in both ‘pango’ and ‘pango-next’, leading to:
--8<---------------cut here---------------start------------->8---
-- Checking for module 'gtk+-3.0'
-- Found gtk+-3.0, version 3.24.30
-- Checking for module 'gdk-3.0'
-- Found gdk-3.0, version 3.24.30
-- Checking for module 'gdk-x11-3.0'
-- Found gdk-x11-3.0, version 3.24.30
-- Checking for module 'gtk4>=4.2'
-- Package 'gtk4' requires 'pango >= 1.50.0' but version of pango is 1.48.10
CMake Error at /gnu/store/zga679c4nldah9l8dhd5a4hdy820hcyf-cmake-minimal-3.21.4/share/cmake-3.21/Modules/FindPkgConfig.cmake:562 (message):
A required package was not found
Call Stack (most recent call first):
/gnu/store/zga679c4nldah9l8dhd5a4hdy820hcyf-cmake-minimal-3.21.4/share/cmake-3.21/Modules/FindPkgConfig.cmake:784 (_pkg_check_modules_internal)
gtk4/CMakeLists.txt:10 (pkg_check_modules)
--8<---------------cut here---------------end--------------->8---
Solutions that come to mind:
1. Disable the GTK 4 backend of ‘fcitx5-gtk’.
2. Add ‘pango-next’ as an input of ‘fcitx5-gtk’, taking precedence
over ‘pango’, at the risk of breaking the GTK+2 and GTK+3
backends.
3. There is no 3rd idea.
Thoughts?
Ludo’.
next prev parent reply other threads:[~2022-03-18 22:49 UTC|newest]
Thread overview: 27+ 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-11 16:03 ` Maxime Devos
2022-03-15 15:42 ` Zhu Zihao
2022-03-18 22:48 ` Ludovic Courtès [this message]
2022-03-19 3:00 ` [bug#54261] [PATCH]: Update GTK to 4.6.1 Zhu Zihao
2022-03-21 1:17 ` Zhu Zihao
2022-03-27 3:04 ` Zhu Zihao
2022-03-27 7:38 ` Liliana Marie Prikler
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
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=87y216op22.fsf_-_@gnu.org \
--to=ludo@gnu.org \
--cc=54261@debbugs.gnu.org \
--cc=all_but_last@163.com \
--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 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).