From: "Andrew Ammerlaan" <andrewammerlaan@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/shiboken2/
Date: Sun, 18 Jul 2021 10:23:22 +0000 (UTC) [thread overview]
Message-ID: <1626603798.f2581accf1511bcaf956b483217d9d67d022c75c.andrewammerlaan@gentoo> (raw)
commit: f2581accf1511bcaf956b483217d9d67d022c75c
Author: Andrew Ammerlaan <andrewammerlaan <AT> gentoo <DOT> org>
AuthorDate: Sun Jul 18 10:21:07 2021 +0000
Commit: Andrew Ammerlaan <andrewammerlaan <AT> gentoo <DOT> org>
CommitDate: Sun Jul 18 10:23:18 2021 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=f2581acc
dev-python/shiboken2: depend on clang-runtime
pyside2 fails to compile if we try to compile it with a
different version of clang then was present when shiboken2
was compiled. Even a change of the minor version triggers
this! We depend on clang-runtime as well as on clang,
because clang-PV pulls in clang-runtime-PV and the
clang-runtime ebuild defines different slots even for the
minor releases (which clang does not, it only has slots
for major releases). This should trigger a rebuild of
shiboken2 even for minor version changes of clang(-runtime)
and thus avoid any issues when compiling pyside2.
Closes: https://bugs.gentoo.org/796614
Package-Manager: Portage-3.0.20, Repoman-3.0.3
RepoMan-Options: --force
Signed-off-by: Andrew Ammerlaan <andrewammerlaan <AT> gentoo.org>
.../shiboken2/{shiboken2-5.15.1.ebuild => shiboken2-5.15.1-r1.ebuild} | 3 ++-
.../shiboken2/{shiboken2-5.15.2.ebuild => shiboken2-5.15.2-r1.ebuild} | 3 ++-
2 files changed, 4 insertions(+), 2 deletions(-)
diff --git a/dev-python/shiboken2/shiboken2-5.15.1.ebuild b/dev-python/shiboken2/shiboken2-5.15.1-r1.ebuild
similarity index 99%
rename from dev-python/shiboken2/shiboken2-5.15.1.ebuild
rename to dev-python/shiboken2/shiboken2-5.15.1-r1.ebuild
index 7acae0aa868..de2845464e8 100644
--- a/dev-python/shiboken2/shiboken2-5.15.1.ebuild
+++ b/dev-python/shiboken2/shiboken2-5.15.1-r1.ebuild
@@ -41,7 +41,8 @@ QT_PV="$(ver_cut 1-2):5"
# Since Clang is required at both build- and runtime, BDEPEND is omitted here.
RDEPEND="${PYTHON_DEPS}
>=dev-qt/qtcore-${QT_PV}
- >=sys-devel/clang-6:=
+ sys-devel/clang:=
+ sys-devel/clang-runtime:=
docstrings? (
>=dev-libs/libxml2-2.6.32
>=dev-libs/libxslt-1.1.19
diff --git a/dev-python/shiboken2/shiboken2-5.15.2.ebuild b/dev-python/shiboken2/shiboken2-5.15.2-r1.ebuild
similarity index 99%
rename from dev-python/shiboken2/shiboken2-5.15.2.ebuild
rename to dev-python/shiboken2/shiboken2-5.15.2-r1.ebuild
index 0f97bbc648a..cbfac4a28fb 100644
--- a/dev-python/shiboken2/shiboken2-5.15.2.ebuild
+++ b/dev-python/shiboken2/shiboken2-5.15.2-r1.ebuild
@@ -44,7 +44,8 @@ QT_PV="$(ver_cut 1-2):5"
# Since Clang is required at both build- and runtime, BDEPEND is omitted here.
RDEPEND="${PYTHON_DEPS}
>=dev-qt/qtcore-${QT_PV}
- >=sys-devel/clang-6:=
+ sys-devel/clang:=
+ sys-devel/clang-runtime:=
docstrings? (
>=dev-libs/libxml2-2.6.32
>=dev-libs/libxslt-1.1.19
next reply other threads:[~2021-07-18 10:23 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-18 10:23 Andrew Ammerlaan [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-06-06 16:43 [gentoo-commits] repo/gentoo:master commit in: dev-python/shiboken2/ Andreas Sturmlechner
2024-06-01 15:59 Arthur Zamarin
2024-06-01 10:25 Arthur Zamarin
2024-05-30 15:35 Andrew Ammerlaan
2024-04-04 4:23 Arthur Zamarin
2024-04-03 20:45 Arthur Zamarin
2024-03-24 20:38 Andrew Ammerlaan
2024-02-11 14:38 Andrew Ammerlaan
2024-02-01 23:37 Andreas Sturmlechner
2024-01-31 7:18 Joonas Niilola
2024-01-29 4:22 Ionen Wolkens
2024-01-03 12:02 Andrew Ammerlaan
2023-12-03 5:45 Arthur Zamarin
2023-10-09 10:41 Andrew Ammerlaan
2023-10-06 7:43 Andrew Ammerlaan
2023-10-03 15:27 Andrew Ammerlaan
2023-10-03 14:27 Andrew Ammerlaan
2023-09-11 6:48 Jakov Smolić
2023-07-24 22:50 Sam James
2023-07-24 21:02 Sam James
2023-07-24 12:56 Michał Górny
2023-06-14 19:59 Andrew Ammerlaan
2023-05-27 13:42 Arthur Zamarin
2023-05-26 7:18 Sam James
2023-05-23 17:50 Arthur Zamarin
2023-04-11 18:12 Andrew Ammerlaan
2023-03-05 11:05 Michał Górny
2023-03-05 7:39 Arthur Zamarin
2023-02-07 17:47 Sam James
2023-02-07 16:54 Sam James
2023-01-28 19:56 Michał Górny
2023-01-28 18:58 Arthur Zamarin
2022-12-04 23:31 Sam James
2022-12-04 21:32 Sam James
2022-11-07 11:05 Andrew Ammerlaan
2022-11-04 8:38 Michał Górny
2022-11-04 8:16 Agostino Sarubbo
2022-11-03 22:04 Sam James
2022-11-03 19:18 Arthur Zamarin
2022-10-24 5:14 Michał Górny
2022-09-23 11:26 Andrew Ammerlaan
2022-09-01 19:13 Sam James
2022-08-29 14:31 Sam James
2022-08-13 14:18 Andrew Ammerlaan
2022-08-12 15:13 Andrew Ammerlaan
2022-08-03 9:00 Michał Górny
2022-08-03 4:38 Arthur Zamarin
2022-08-02 20:27 Sam James
2022-08-02 20:27 Sam James
2022-07-18 10:22 Sam James
2022-02-25 18:53 Arthur Zamarin
2021-10-17 9:41 Michał Górny
2021-09-03 1:53 Sam James
2021-07-19 18:36 Sam James
2021-07-19 18:36 Sam James
2021-07-05 22:35 Sam James
2021-06-02 17:31 Rick Farina
2021-06-01 17:07 Andrew Ammerlaan
2021-05-30 9:45 Agostino Sarubbo
2021-05-18 6:29 Agostino Sarubbo
2021-02-21 8:06 Sam James
2020-10-14 15:38 Rick Farina
2020-10-14 15:38 Rick Farina
2020-05-22 17:23 Rick Farina
2020-05-22 17:23 Rick Farina
2020-05-22 17:23 Rick Farina
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=1626603798.f2581accf1511bcaf956b483217d9d67d022c75c.andrewammerlaan@gentoo \
--to=andrewammerlaan@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