From: "Joonas Niilola" <juippis@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-util/shards/
Date: Thu, 26 Aug 2021 10:51:59 +0000 (UTC) [thread overview]
Message-ID: <1629975094.f2123c47a7f5789c28e5294249e31db2c5fb759a.juippis@gentoo> (raw)
commit: f2123c47a7f5789c28e5294249e31db2c5fb759a
Author: toshokan <toshokan <AT> shojigate <DOT> net>
AuthorDate: Tue Aug 24 03:39:51 2021 +0000
Commit: Joonas Niilola <juippis <AT> gentoo <DOT> org>
CommitDate: Thu Aug 26 10:51:34 2021 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=f2123c47
dev-util/shards: Depend on libyaml, drop old
Package-Manager: Portage-3.0.20, Repoman-3.0.3
Signed-off-by: Jason Pizzuco <toshokan <AT> shojigate.net>
Closes: https://github.com/gentoo/gentoo/pull/21848
Signed-off-by: Joonas Niilola <juippis <AT> gentoo.org>
dev-util/shards/{shards-0.15.0.ebuild => shards-0.15.0-r1.ebuild} | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/dev-util/shards/shards-0.15.0.ebuild b/dev-util/shards/shards-0.15.0-r1.ebuild
similarity index 95%
rename from dev-util/shards/shards-0.15.0.ebuild
rename to dev-util/shards/shards-0.15.0-r1.ebuild
index 52270b880ee..cd40186df45 100644
--- a/dev-util/shards/shards-0.15.0.ebuild
+++ b/dev-util/shards/shards-0.15.0-r1.ebuild
@@ -20,7 +20,8 @@ SLOT="0"
KEYWORDS="~amd64"
DEPEND="
- >dev-lang/crystal-0.11.1[yaml]
+ >dev-lang/crystal-0.11.1
+ dev-libs/libyaml
"
RDEPEND="${DEPEND}"
next reply other threads:[~2021-08-26 10:52 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-26 10:51 Joonas Niilola [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-05-01 16:48 [gentoo-commits] repo/gentoo:master commit in: dev-util/shards/ Sam James
2024-03-30 23:09 Maciej Barć
2024-03-30 23:09 Maciej Barć
2024-01-28 6:50 Sam James
2023-12-27 1:20 Maciej Barć
2023-06-25 8:07 Maciej Barć
2023-06-25 8:07 Maciej Barć
2023-05-19 17:45 Sam James
2023-04-16 10:02 Maciej Barć
2023-03-26 2:57 Sam James
2023-03-04 7:45 Arthur Zamarin
2023-02-12 0:48 Maciej Barć
2023-02-12 0:48 Maciej Barć
2023-02-11 18:54 Jonas Stein
2021-08-01 6:39 Joonas Niilola
2021-07-23 7:33 Sergei Trofimovich
2021-07-17 11:22 Sergei Trofimovich
2021-06-30 6:39 Sergei Trofimovich
2021-03-13 9:53 Sergei Trofimovich
2021-03-11 7:49 Sergei Trofimovich
2021-02-26 10:25 Sergei Trofimovich
2021-02-24 8:16 Sergei Trofimovich
2021-01-28 8:09 Sergei Trofimovich
2021-01-23 11:28 Sergei Trofimovich
2020-08-09 18:35 Sergei Trofimovich
2020-08-08 9:58 Sergei Trofimovich
2020-08-06 21:31 Sergei Trofimovich
2020-06-20 19:49 Sergei Trofimovich
2020-06-09 6:42 Sergei Trofimovich
2020-06-06 8:56 Sergei Trofimovich
2020-05-29 22:13 Sergei Trofimovich
2020-05-23 10:13 Sergei Trofimovich
2020-03-25 22:41 Sergei Trofimovich
2020-02-12 22:32 Sergei Trofimovich
2019-06-14 18:32 Sergei Trofimovich
2018-06-17 21:48 Sergei Trofimovich
2018-06-08 15:36 Sergei Trofimovich
2018-06-08 15:36 Sergei Trofimovich
2018-05-19 16:10 Jonas Stein
2018-01-09 23:09 Sergei Trofimovich
2016-11-25 8:57 Sergei Trofimovich
2016-09-02 16:38 Sergei Trofimovich
2016-07-30 9:50 Sergei Trofimovich
2016-03-20 22:59 Patrice Clement
2016-02-24 21:38 Patrice Clement
2016-02-24 21:38 Patrice Clement
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=1629975094.f2123c47a7f5789c28e5294249e31db2c5fb759a.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