From: "Conrad Kostecki" <conikost@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-lua/luacheck/
Date: Wed, 21 Apr 2021 21:03:32 +0000 (UTC) [thread overview]
Message-ID: <1619038970.162440b37abf1087555a653cbc3a50184d6a944e.conikost@gentoo> (raw)
commit: 162440b37abf1087555a653cbc3a50184d6a944e
Author: Conrad Kostecki <conikost <AT> gentoo <DOT> org>
AuthorDate: Wed Apr 21 20:55:43 2021 +0000
Commit: Conrad Kostecki <conikost <AT> gentoo <DOT> org>
CommitDate: Wed Apr 21 21:02:50 2021 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=162440b3
dev-lua/luacheck: add missing cliargs for test
Bug: https://bugs.gentoo.org/784848
Package-Manager: Portage-3.0.18, Repoman-3.0.3
Signed-off-by: Conrad Kostecki <conikost <AT> gentoo.org>
dev-lua/luacheck/luacheck-0.24.0.ebuild | 1 +
1 file changed, 1 insertion(+)
diff --git a/dev-lua/luacheck/luacheck-0.24.0.ebuild b/dev-lua/luacheck/luacheck-0.24.0.ebuild
index baaa8dfdfa5..b74b9ffb905 100644
--- a/dev-lua/luacheck/luacheck-0.24.0.ebuild
+++ b/dev-lua/luacheck/luacheck-0.24.0.ebuild
@@ -30,6 +30,7 @@ BDEPEND="
doc? ( dev-python/sphinx )
test? (
dev-lua/busted[${LUA_USEDEP}]
+ dev-lua/lua_cliargs[${LUA_USEDEP}]
${RDEPEND}
)
"
next reply other threads:[~2021-04-21 21:03 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-21 21:03 Conrad Kostecki [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-06-27 15:40 [gentoo-commits] repo/gentoo:master commit in: dev-lua/luacheck/ Conrad Kostecki
2024-06-27 15:40 Conrad Kostecki
2024-05-24 23:35 Conrad Kostecki
2024-01-14 2:39 Conrad Kostecki
2024-01-14 2:39 Conrad Kostecki
2023-12-12 22:16 Conrad Kostecki
2023-12-12 22:16 Conrad Kostecki
2023-07-26 0:55 Sam James
2023-06-24 21:36 Conrad Kostecki
2023-01-31 15:17 Conrad Kostecki
2023-01-31 15:17 Conrad Kostecki
2022-12-20 22:03 Conrad Kostecki
2022-12-20 22:03 Conrad Kostecki
2022-11-25 17:59 Conrad Kostecki
2022-03-12 11:54 Conrad Kostecki
2022-03-12 11:54 Conrad Kostecki
2021-09-18 12:29 Marek Szuba
2021-05-25 16:21 Georgy Yakovlev
2021-04-22 19:31 Sergei Trofimovich
2021-04-20 21:20 Sergei Trofimovich
2021-04-16 21:29 Conrad Kostecki
2021-04-16 21:29 Conrad Kostecki
2021-04-16 21:29 Conrad Kostecki
2021-03-16 17:37 Conrad Kostecki
2021-01-27 19:48 Conrad Kostecki
2021-01-11 8:01 Sam James
2021-01-09 16:22 Sam James
2020-12-17 14:17 Conrad Kostecki
2020-12-17 13:53 Conrad Kostecki
2020-12-17 13:09 Conrad Kostecki
2020-12-17 13:09 Conrad Kostecki
2020-12-17 12:48 Sam James
2020-12-03 13:50 Marek Szuba
2020-12-03 5:04 Sam James
2020-11-30 13:33 Conrad Kostecki
2020-11-29 17:11 Sergei Trofimovich
2020-11-29 1:37 Conrad Kostecki
2020-11-29 1:33 Conrad Kostecki
2020-11-29 1:33 Conrad Kostecki
2020-11-29 1:33 Conrad Kostecki
2020-11-29 1:33 Conrad Kostecki
2020-09-04 23:31 Sam James
2020-03-15 23:36 Georgy Yakovlev
2020-03-15 23:31 Georgy Yakovlev
2020-03-15 23:31 Georgy Yakovlev
2019-07-29 14:41 Mikle Kolyada
2019-05-24 22:51 Sergei Trofimovich
2019-05-24 22:08 Sergei Trofimovich
2019-05-12 20:56 Thomas Deutschmann
2018-07-07 12:15 Jonas Stein
2018-04-21 22:56 Aaron Bauman
2018-04-21 16:00 Mikle Kolyada
2018-04-01 11:48 Mikle Kolyada
2018-03-27 8:06 Sergei Trofimovich
2018-03-27 7:31 Sergei Trofimovich
2017-09-02 8:45 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=1619038970.162440b37abf1087555a653cbc3a50184d6a944e.conikost@gentoo \
--to=conikost@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