From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: metadata/install-qa-check.d/
Date: Wed, 3 Aug 2022 04:27:25 +0000 (UTC) [thread overview]
Message-ID: <1659500819.83a5cad812cdce67994d3c44105e18f443d9a106.sam@gentoo> (raw)
commit: 83a5cad812cdce67994d3c44105e18f443d9a106
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Wed Aug 3 04:26:59 2022 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Wed Aug 3 04:26:59 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=83a5cad8
metadata/install-qa-check.d: drop -b from has_version in 60python-pyc
Only for EAPI 7+, duh. Not going with the faff of --host-root for EAPI
6 etc for now given it's just an optional check.
Signed-off-by: Sam James <sam <AT> gentoo.org>
metadata/install-qa-check.d/60python-pyc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/metadata/install-qa-check.d/60python-pyc b/metadata/install-qa-check.d/60python-pyc
index 37b0acaf7e0a..f2d5ff3452dd 100644
--- a/metadata/install-qa-check.d/60python-pyc
+++ b/metadata/install-qa-check.d/60python-pyc
@@ -19,7 +19,7 @@ python_pyc_check() {
# Avoid running the check if sufficiently new gpep517 is not installed
# yet. It's valid to schedule (for merge order) >=gpep517-8 after
# packages which have this check run if they don't use distutils-r1.
- has_version -b ">=dev-python/gpep517-8" || return
+ has_version ">=dev-python/gpep517-8" || return
for prog in "${progs[@]}"; do
local impl=${prog%/*}
next reply other threads:[~2022-08-03 4:27 UTC|newest]
Thread overview: 77+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-03 4:27 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-21 15:12 [gentoo-commits] repo/gentoo:master commit in: metadata/install-qa-check.d/ Michał Górny
2024-09-05 8:43 Michał Górny
2024-03-29 18:47 Sam James
2024-01-08 14:48 Michał Górny
2024-01-08 14:48 Michał Górny
2024-01-08 14:48 Michał Górny
2024-01-08 14:48 Michał Górny
2024-01-08 14:48 Michał Górny
2024-01-08 14:48 Michał Górny
2024-01-08 14:48 Michał Górny
2024-01-08 14:48 Michał Górny
2024-01-08 14:48 Michał Górny
2023-08-17 22:08 Ulrich Müller
2023-05-17 3:40 Michał Górny
2022-09-19 3:52 Sam James
2022-08-21 2:31 Sam James
2022-08-04 23:49 Sam James
2022-08-03 18:56 Sam James
2022-08-03 1:53 Sam James
2022-08-02 4:08 Michał Górny
2022-07-16 11:26 Michał Górny
2022-06-08 0:25 Mike Gilbert
2022-05-06 12:48 Ionen Wolkens
2022-05-05 23:38 Sam James
2022-05-02 6:01 Agostino Sarubbo
2022-04-30 19:13 Sam James
2022-04-28 3:06 Sam James
2022-04-27 0:13 Sam James
2022-04-26 23:45 Sam James
2022-04-26 15:32 Sam James
2022-04-19 18:31 Sam James
2022-04-19 18:31 Sam James
2022-04-17 14:21 Sam James
2022-04-17 14:18 Sam James
2022-03-04 1:26 Sam James
2022-03-04 1:26 Sam James
2022-02-01 18:19 Mike Gilbert
2022-02-01 1:37 Mike Gilbert
2022-01-16 9:40 Michał Górny
2021-08-19 1:35 Sam James
2021-08-16 2:12 Sam James
2021-08-16 2:12 Sam James
2021-08-16 2:12 Sam James
2021-08-16 2:12 Sam James
2021-08-02 8:17 Michał Górny
2021-07-03 8:16 Michał Górny
2021-07-01 8:57 Georgy Yakovlev
2021-06-28 18:47 Georgy Yakovlev
2021-06-28 8:56 Georgy Yakovlev
2021-06-28 0:12 Georgy Yakovlev
2021-06-27 2:08 Sam James
2021-06-26 23:25 Georgy Yakovlev
2021-06-26 23:09 Georgy Yakovlev
2021-05-29 15:15 Michał Górny
2021-05-25 5:13 Michał Górny
2021-04-29 11:42 Michał Górny
2021-04-29 11:42 Michał Górny
2021-04-29 11:42 Michał Górny
2021-04-29 11:42 Michał Górny
2021-04-09 23:17 Sam James
2020-10-17 19:01 Michał Górny
2020-10-16 7:42 Michał Górny
2020-09-22 11:12 Michał Górny
2020-09-22 7:33 Michał Górny
2020-09-22 7:00 Michał Górny
2020-09-22 7:00 Michał Górny
2020-09-21 17:48 Michał Górny
2020-09-21 15:30 Michał Górny
2020-02-13 18:59 Georgy Yakovlev
2020-01-20 20:45 Michael Orlitzky
2019-12-30 16:10 Michał Górny
2019-11-12 7:53 Sergei Trofimovich
2019-11-11 23:05 Zac Medico
2019-11-11 22:25 Sergei Trofimovich
2019-11-01 13:16 Michał Górny
2018-10-06 8:35 Michał Górny
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=1659500819.83a5cad812cdce67994d3c44105e18f443d9a106.sam@gentoo \
--to=sam@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