From: "Joonas Niilola" <juippis@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: gui-libs/gtk-layer-shell/
Date: Fri, 11 Nov 2022 18:13:02 +0000 (UTC) [thread overview]
Message-ID: <1668190379.52e7f1edbe3c874887bde17824e83bf6597d7029.juippis@gentoo> (raw)
commit: 52e7f1edbe3c874887bde17824e83bf6597d7029
Author: Joonas Niilola <juippis <AT> gentoo <DOT> org>
AuthorDate: Fri Nov 11 18:07:35 2022 +0000
Commit: Joonas Niilola <juippis <AT> gentoo <DOT> org>
CommitDate: Fri Nov 11 18:12:59 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=52e7f1ed
gui-libs/gtk-layer-shell: enable py3.11 on 0.8.0
- and ass missing BDEPEND for xorg-proto.
Signed-off-by: Joonas Niilola <juippis <AT> gentoo.org>
gui-libs/gtk-layer-shell/gtk-layer-shell-0.8.0.ebuild | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/gui-libs/gtk-layer-shell/gtk-layer-shell-0.8.0.ebuild b/gui-libs/gtk-layer-shell/gtk-layer-shell-0.8.0.ebuild
index 97c8b95bf9be..af38d280c13d 100644
--- a/gui-libs/gtk-layer-shell/gtk-layer-shell-0.8.0.ebuild
+++ b/gui-libs/gtk-layer-shell/gtk-layer-shell-0.8.0.ebuild
@@ -3,7 +3,7 @@
EAPI=8
-PYTHON_COMPAT=( python3_{8..10} )
+PYTHON_COMPAT=( python3_{8..11} )
VALA_USE_DEPEND="vapigen"
inherit vala meson python-any-r1
@@ -34,6 +34,7 @@ RDEPEND="${DEPEND}"
BDEPEND="
dev-util/wayland-scanner
virtual/pkgconfig
+ x11-base/xorg-proto
gtk-doc? ( dev-util/gtk-doc )
test? ( ${PYTHON_DEPS} )
vala? ( $(vala_depend) )
next reply other threads:[~2022-11-11 18:13 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-11 18:13 Joonas Niilola [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-04-26 5:28 [gentoo-commits] repo/gentoo:master commit in: gui-libs/gtk-layer-shell/ Sam James
2025-04-26 2:36 Sam James
2025-04-26 2:14 Sam James
2025-04-10 9:44 Sam James
2025-04-10 9:44 Sam James
2025-03-12 23:29 Sam James
2025-03-12 23:21 Sam James
2025-03-12 23:13 Sam James
2025-03-12 23:13 Sam James
2025-03-12 23:13 Sam James
2025-03-12 23:13 Sam James
2024-10-29 21:47 James Le Cuirot
2024-03-23 7:16 Arthur Zamarin
2024-03-23 7:16 Arthur Zamarin
2024-03-22 16:31 Arthur Zamarin
2024-03-22 16:31 Arthur Zamarin
2024-03-22 16:29 Arthur Zamarin
2024-03-22 16:29 Arthur Zamarin
2024-03-22 16:03 Arthur Zamarin
2024-03-22 16:03 Arthur Zamarin
2024-02-28 6:55 Joonas Niilola
2024-02-09 13:04 Joonas Niilola
2024-01-30 5:38 Sam James
2024-01-30 5:38 Sam James
2024-01-30 5:13 Sam James
2024-01-30 5:13 Sam James
2024-01-30 5:13 Sam James
2024-01-30 5:13 Sam James
2024-01-20 13:10 Sam James
2023-12-30 1:26 Ionen Wolkens
2023-12-22 15:36 Arthur Zamarin
2023-12-22 5:14 Ionen Wolkens
2023-12-02 10:53 Arthur Zamarin
2023-12-02 9:34 Michał Górny
2023-09-11 21:52 Sam James
2023-04-16 6:56 Sam James
2023-04-16 6:56 Sam James
2023-04-16 6:56 Sam James
2023-04-01 16:07 Arthur Zamarin
2023-03-17 11:33 Michał Górny
2023-02-25 14:01 Sam James
2023-02-25 14:01 Sam James
2023-01-14 10:00 Arthur Zamarin
2023-01-13 14:19 Arthur Zamarin
2023-01-13 11:51 Arthur Zamarin
2022-11-11 18:13 Joonas Niilola
2022-07-29 3:16 Sam James
2022-07-29 3:16 Sam James
2021-11-12 1:31 Sam James
2021-11-12 1:31 Sam James
2021-09-18 14:42 Yixun Lan
2020-07-09 12:50 Sam James
2020-07-02 22:36 Georgy Yakovlev
2020-04-28 19:23 Mart Raudsepp
2020-04-28 1:22 Adam Feldman
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=1668190379.52e7f1edbe3c874887bde17824e83bf6597d7029.juippis@gentoo \
--to=juippis@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