From: "Marek Szuba" <marecki@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-lua/luarocks/
Date: Mon, 30 Nov 2020 01:08:37 +0000 (UTC) [thread overview]
Message-ID: <1606698503.f05098a0f77bedfe4259412a9f1b8de0936c4ff1.marecki@gentoo> (raw)
commit: f05098a0f77bedfe4259412a9f1b8de0936c4ff1
Author: Marek Szuba <marecki <AT> gentoo <DOT> org>
AuthorDate: Mon Nov 30 00:32:14 2020 +0000
Commit: Marek Szuba <marecki <AT> gentoo <DOT> org>
CommitDate: Mon Nov 30 01:08:23 2020 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=f05098a0
dev-lua/luarocks: remove dev-lua/busted{,-htest} version requirement
The LUA_USEDEP bit is sufficient to pull in a version migrated to Lua
eclasses, regardless of whether either of these gets updated to a new
release before we unmask slotted Lua or not.
Signed-off-by: Marek Szuba <marecki <AT> gentoo.org>
dev-lua/luarocks/luarocks-3.4.0-r100.ebuild | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/dev-lua/luarocks/luarocks-3.4.0-r100.ebuild b/dev-lua/luarocks/luarocks-3.4.0-r100.ebuild
index 3b7a34e19e0..ac482071bc6 100644
--- a/dev-lua/luarocks/luarocks-3.4.0-r100.ebuild
+++ b/dev-lua/luarocks/luarocks-3.4.0-r100.ebuild
@@ -30,8 +30,8 @@ DEPEND="
BDEPEND="
virtual/pkgconfig
test? (
- $(lua_gen_cond_dep '>=dev-lua/busted-2.0.0-r100[${LUA_USEDEP}]')
- $(lua_gen_cond_dep '>=dev-lua/busted-htest-1.0.0-r100[${LUA_USEDEP}]')
+ $(lua_gen_cond_dep 'dev-lua/busted[${LUA_USEDEP}]')
+ $(lua_gen_cond_dep 'dev-lua/busted-htest[${LUA_USEDEP}]')
${RDEPEND}
)
"
next reply other threads:[~2020-11-30 1:08 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-30 1:08 Marek Szuba [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-03-01 1:14 [gentoo-commits] repo/gentoo:master commit in: dev-lua/luarocks/ Conrad Kostecki
2025-03-01 1:14 Conrad Kostecki
2024-06-22 20:01 Conrad Kostecki
2024-06-17 22:31 Conrad Kostecki
2024-06-17 22:31 Conrad Kostecki
2024-04-19 11:19 Arthur Zamarin
2024-04-17 23:35 Sam James
2024-04-17 22:10 Sam James
2024-04-17 22:02 Sam James
2024-03-15 23:59 Conrad Kostecki
2024-03-09 13:57 Conrad Kostecki
2023-02-21 17:55 Conrad Kostecki
2023-02-21 6:51 Sam James
2023-02-21 5:14 Sam James
2023-02-21 5:14 Sam James
2023-02-21 5:14 Sam James
2022-12-10 13:27 Conrad Kostecki
2022-08-05 7:52 Conrad Kostecki
2022-08-04 8:03 Agostino Sarubbo
2022-08-04 0:13 Sam James
2022-08-04 0:13 Sam James
2022-08-03 20:37 Arthur Zamarin
2022-07-02 14:58 Conrad Kostecki
2022-05-20 15:34 Conrad Kostecki
2022-05-19 7:49 Agostino Sarubbo
2022-05-19 7:47 Agostino Sarubbo
2022-05-19 1:20 Sam James
2022-05-19 1:20 Sam James
2022-04-17 14:01 Conrad Kostecki
2021-12-24 15:59 Conrad Kostecki
2021-12-24 15:52 Arthur Zamarin
2021-12-24 4:55 Sam James
2021-12-23 10:33 Jakov Smolić
2021-12-23 10:33 Jakov Smolić
2021-11-22 21:24 Conrad Kostecki
2021-06-03 21:47 Conrad Kostecki
2021-06-03 19:58 Sam James
2021-06-03 16:26 Sam James
2021-06-02 1:13 Sam James
2021-05-25 16:21 Georgy Yakovlev
2021-04-30 17:42 Mikle Kolyada
2021-04-22 19:31 Sergei Trofimovich
2021-04-20 21:20 Sergei Trofimovich
2021-04-14 20:08 Conrad Kostecki
2021-04-14 20:08 Conrad Kostecki
2021-04-01 16:22 Conrad Kostecki
2021-03-16 17:37 Conrad Kostecki
2021-01-27 19:48 Conrad Kostecki
2021-01-23 22:51 Sam James
2021-01-09 14:29 Conrad Kostecki
2021-01-09 14:29 Conrad Kostecki
2020-12-03 13:50 Marek Szuba
2020-12-01 12:16 Conrad Kostecki
2020-11-30 10:06 Conrad Kostecki
2020-11-30 1:08 Marek Szuba
2020-11-30 1:08 Marek Szuba
2020-11-30 1:08 Marek Szuba
2020-11-30 0:18 Conrad Kostecki
2020-09-13 9:16 Sam James
2020-09-13 7:04 Sam James
2020-09-08 15:56 Thomas Deutschmann
2020-03-15 22:30 Georgy Yakovlev
2020-03-15 22:28 Georgy Yakovlev
2020-03-15 22:28 Georgy Yakovlev
2020-03-15 22:28 Georgy Yakovlev
2020-01-09 18:41 Rafael Martins
2019-11-24 2:49 Aaron Bauman
2016-12-20 13:40 Tobias Klausmann
2016-08-06 10:51 Pacho Ramos
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=1606698503.f05098a0f77bedfe4259412a9f1b8de0936c4ff1.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