From: "Arthur Zamarin" <arthurzam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-libs/c-blosc2/
Date: Sat, 29 Apr 2023 15:31:07 +0000 (UTC) [thread overview]
Message-ID: <1682782256.a58723c3fffb4638bcb97affe0e44e48fc7af2b0.arthurzam@gentoo> (raw)
commit: a58723c3fffb4638bcb97affe0e44e48fc7af2b0
Author: Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
AuthorDate: Sat Apr 29 15:30:56 2023 +0000
Commit: Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
CommitDate: Sat Apr 29 15:30:56 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a58723c3
dev-libs/c-blosc2: Stabilize 2.6.1 amd64, #894906
Signed-off-by: Arthur Zamarin <arthurzam <AT> gentoo.org>
dev-libs/c-blosc2/c-blosc2-2.6.1.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-libs/c-blosc2/c-blosc2-2.6.1.ebuild b/dev-libs/c-blosc2/c-blosc2-2.6.1.ebuild
index 2ec6c5fa11f0..d66fbe0c5084 100644
--- a/dev-libs/c-blosc2/c-blosc2-2.6.1.ebuild
+++ b/dev-libs/c-blosc2/c-blosc2-2.6.1.ebuild
@@ -17,7 +17,7 @@ SRC_URI="
LICENSE="BSD"
SLOT="0/1"
-KEYWORDS="~amd64 ~arm arm64 ~hppa ~ia64 ~ppc ~ppc64 ~riscv ~s390 ~sparc ~x86 ~amd64-linux ~x86-linux"
+KEYWORDS="amd64 ~arm arm64 ~hppa ~ia64 ~ppc ~ppc64 ~riscv ~s390 ~sparc ~x86 ~amd64-linux ~x86-linux"
IUSE="test zlib zstd"
REQUIRED_USE="test? ( zlib zstd )"
RESTRICT="!test? ( test )"
next reply other threads:[~2023-04-29 15:31 UTC|newest]
Thread overview: 77+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-29 15:31 Arthur Zamarin [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-12-16 8:07 [gentoo-commits] repo/gentoo:master commit in: dev-libs/c-blosc2/ Michał Górny
2024-12-15 7:02 Sam James
2024-12-14 17:25 Arthur Zamarin
2024-12-14 13:20 Arthur Zamarin
2024-12-14 10:35 Arthur Zamarin
2024-09-12 11:25 Michał Górny
2024-09-12 8:07 Arthur Zamarin
2024-08-31 10:51 Arthur Zamarin
2024-08-31 7:31 Sam James
2024-08-31 7:22 Michał Górny
2024-08-31 7:20 Arthur Zamarin
2024-07-31 5:52 Michał Górny
2024-04-27 8:04 Arthur Zamarin
2024-04-27 7:40 Michał Górny
2024-04-27 7:40 Michał Górny
2024-04-27 7:40 Michał Górny
2024-04-27 7:40 Michał Górny
2024-04-11 4:25 Michał Górny
2024-04-11 4:25 Michał Górny
2024-04-06 15:01 Michał Górny
2024-04-04 18:09 Michał Górny
2024-04-02 5:16 Michał Górny
2024-04-02 5:16 Michał Górny
2024-02-24 19:22 Arthur Zamarin
2024-02-24 14:04 Sam James
2024-02-24 10:07 Sam James
2024-02-24 9:43 Michał Górny
2024-02-08 4:22 Michał Górny
2024-01-26 5:39 Michał Górny
2024-01-24 18:56 Michał Górny
2024-01-04 11:29 WANG Xuerui
2023-12-29 4:38 Michał Górny
2023-12-21 7:27 Arthur Zamarin
2023-12-21 6:52 Sam James
2023-12-21 6:52 Sam James
2023-12-21 6:52 Sam James
2023-12-02 11:13 Arthur Zamarin
2023-12-02 10:43 Michał Górny
2023-12-02 10:21 Arthur Zamarin
2023-12-02 10:14 Arthur Zamarin
2023-12-01 5:39 Michał Górny
2023-11-07 20:20 Michał Górny
2023-11-07 19:54 Arthur Zamarin
2023-11-07 19:51 Arthur Zamarin
2023-11-07 19:22 Michał Górny
2023-11-05 13:28 Michał Górny
2023-11-05 5:36 Michał Górny
2023-11-02 4:12 Sam James
2023-11-02 4:12 Sam James
2023-11-02 4:12 Sam James
2023-11-01 20:37 Arthur Zamarin
2023-10-06 4:34 Michał Górny
2023-09-28 4:43 Michał Górny
2023-09-13 15:02 Michał Górny
2023-09-02 14:11 Michał Górny
2023-09-02 13:58 Sam James
2023-09-02 13:58 Sam James
2023-09-02 13:58 Sam James
2023-09-02 13:58 Sam James
2023-09-02 13:58 Sam James
2023-09-02 13:58 Sam James
2023-08-20 17:11 Arthur Zamarin
2023-08-20 17:11 Arthur Zamarin
2023-08-20 17:11 Arthur Zamarin
2023-08-20 3:07 Michał Górny
2023-08-20 2:30 Michał Górny
2023-08-02 4:36 Michał Górny
2023-08-01 14:59 Michał Górny
2023-07-05 7:58 Michał Górny
2023-06-21 15:01 Michał Górny
2023-05-19 4:03 Michał Górny
2023-05-16 16:28 Michał Górny
2023-04-29 15:47 Arthur Zamarin
2023-04-29 15:25 Arthur Zamarin
2022-12-29 17:23 Michał Górny
2022-12-28 15:31 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=1682782256.a58723c3fffb4638bcb97affe0e44e48fc7af2b0.arthurzam@gentoo \
--to=arthurzam@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