From: "Marek Szuba" <marecki@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-text/xchm/
Date: Thu, 30 Mar 2023 09:47:02 +0000 (UTC) [thread overview]
Message-ID: <1680169610.e001bde2e3175cf0635b644d90c7e5dc59abe4c4.marecki@gentoo> (raw)
commit: e001bde2e3175cf0635b644d90c7e5dc59abe4c4
Author: Marek Szuba <marecki <AT> gentoo <DOT> org>
AuthorDate: Thu Mar 30 09:32:23 2023 +0000
Commit: Marek Szuba <marecki <AT> gentoo <DOT> org>
CommitDate: Thu Mar 30 09:46:50 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e001bde2
app-text/xchm: add x11-libs/wxGTK version cap to work around Bug #895982
Closes: https://bugs.gentoo.org/895534
Signed-off-by: Marek Szuba <marecki <AT> gentoo.org>
app-text/xchm/xchm-1.35.ebuild | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/app-text/xchm/xchm-1.35.ebuild b/app-text/xchm/xchm-1.35.ebuild
index ed93e6bfae5e..1e6307942d7b 100644
--- a/app-text/xchm/xchm-1.35.ebuild
+++ b/app-text/xchm/xchm-1.35.ebuild
@@ -16,8 +16,9 @@ SLOT="0"
KEYWORDS="~amd64 ~ppc ~riscv ~x86"
IUSE="nls"
+# wxGTK version cap is due to Bug #895982
RDEPEND=">=dev-libs/chmlib-0.36
- x11-libs/wxGTK:${WX_GTK_VER}[X]
+ <x11-libs/wxGTK-3.2.2.1:${WX_GTK_VER}[X]
nls? ( virtual/libintl )"
DEPEND="${RDEPEND}"
BDEPEND="nls? ( sys-devel/gettext )"
next reply other threads:[~2023-03-30 9:47 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-30 9:47 Marek Szuba [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-05-03 18:24 [gentoo-commits] repo/gentoo:master commit in: app-text/xchm/ Arthur Zamarin
2025-04-26 1:25 Sam James
2023-11-21 10:05 Marek Szuba
2023-10-26 16:17 Arthur Zamarin
2023-10-26 16:17 Arthur Zamarin
2023-10-26 16:17 Arthur Zamarin
2023-09-19 12:52 Marek Szuba
2023-06-10 10:35 Marek Szuba
2023-05-27 10:13 Sam James
2023-05-26 20:06 Arthur Zamarin
2023-05-26 20:06 Arthur Zamarin
2023-03-31 16:55 Marek Szuba
2023-02-05 23:03 Marek Szuba
2022-02-24 13:51 Marek Szuba
2022-02-24 13:51 Marek Szuba
2022-02-24 13:02 Sam James
2022-02-24 9:37 Jakov Smolić
2022-02-24 9:36 Jakov Smolić
2022-01-03 23:14 Marek Szuba
2021-09-10 20:51 Marek Szuba
2021-04-28 23:18 Marek Szuba
2021-04-28 18:47 Sam James
2021-04-28 17:00 Sam James
2021-04-27 20:45 Sam James
2021-03-22 12:26 Marek Szuba
2021-03-22 12:26 Marek Szuba
2020-12-24 13:25 Marek Szuba
2020-12-15 10:37 Sam James
2020-12-04 18:31 Sergei Trofimovich
2020-12-02 3:06 Thomas Deutschmann
2020-11-29 23:37 Marek Szuba
2020-11-29 23:12 Marek Szuba
2020-11-29 23:12 Marek Szuba
2020-11-29 23:12 Marek Szuba
2020-11-29 23:12 Marek Szuba
2020-11-29 23:12 Marek Szuba
2020-11-29 22:52 Marek Szuba
2019-11-25 15:09 Jeroen Roovers
2019-11-25 15:09 Jeroen Roovers
2019-08-29 11:39 David Seifert
2019-06-24 9:55 Jeroen Roovers
2019-06-24 9:55 Jeroen Roovers
2019-06-24 9:55 Jeroen Roovers
2019-04-23 7:07 Jeroen Roovers
2019-04-23 7:07 Jeroen Roovers
2019-04-06 9:42 Jeroen Roovers
2019-04-06 8:52 Jeroen Roovers
2019-04-06 8:49 Jeroen Roovers
2019-04-06 8:49 Jeroen Roovers
2019-03-20 13:03 Jeroen Roovers
2019-03-20 13:03 Jeroen Roovers
2019-03-13 9:31 Jeroen Roovers
2018-04-20 20:37 David Seifert
2018-03-10 12:23 Pacho Ramos
2016-11-25 18:57 Pacho Ramos
2016-04-24 8:18 Ryan Hill
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=1680169610.e001bde2e3175cf0635b644d90c7e5dc59abe4c4.marecki@gentoo \
--to=marecki@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox