From: "Ionen Wolkens" <ionen@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-libs/skalibs/
Date: Wed, 17 Jan 2024 02:46:03 +0000 (UTC) [thread overview]
Message-ID: <1705459496.03e543773c7377b83b4cd4433ddb777926078451.ionen@gentoo> (raw)
commit: 03e543773c7377b83b4cd4433ddb777926078451
Author: Matoro Mahri <matoro_gentoo <AT> matoro <DOT> tk>
AuthorDate: Tue Jan 16 20:30:46 2024 +0000
Commit: Ionen Wolkens <ionen <AT> gentoo <DOT> org>
CommitDate: Wed Jan 17 02:44:56 2024 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=03e54377
dev-libs/skalibs: Stabilize 2.14.0.1 arm, #920377
Signed-off-by: Matoro Mahri <matoro_gentoo <AT> matoro.tk>
Signed-off-by: Ionen Wolkens <ionen <AT> gentoo.org>
dev-libs/skalibs/skalibs-2.14.0.1.ebuild | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/dev-libs/skalibs/skalibs-2.14.0.1.ebuild b/dev-libs/skalibs/skalibs-2.14.0.1.ebuild
index 9e658744b9ab..ea5da9db95bb 100644
--- a/dev-libs/skalibs/skalibs-2.14.0.1.ebuild
+++ b/dev-libs/skalibs/skalibs-2.14.0.1.ebuild
@@ -1,4 +1,4 @@
-# Copyright 1999-2023 Gentoo Authors
+# Copyright 1999-2024 Gentoo Authors
# Distributed under the terms of the GNU General Public License v2
EAPI=8
@@ -11,7 +11,7 @@ SRC_URI="https://www.skarnet.org/software/${PN}/${P}.tar.gz"
LICENSE="ISC"
SLOT="0/$(ver_cut 1-2)"
-KEYWORDS="~alpha amd64 ~arm ~arm64 ~mips ~riscv x86"
+KEYWORDS="~alpha amd64 arm ~arm64 ~mips ~riscv x86"
HTML_DOCS=( doc/. )
next reply other threads:[~2024-01-17 2:46 UTC|newest]
Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-17 2:46 Ionen Wolkens [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-24 9:39 [gentoo-commits] repo/gentoo:master commit in: dev-libs/skalibs/ Petr Vaněk
2024-08-30 10:19 Petr Vaněk
2024-07-15 10:54 Sam James
2024-07-15 10:53 Sam James
2024-07-15 10:53 Sam James
2024-06-14 13:31 Petr Vaněk
2024-06-09 21:12 Sam James
2024-06-09 21:12 Sam James
2024-03-03 11:19 Petr Vaněk
2024-03-03 10:33 Jakov Smolić
2024-03-03 10:33 Jakov Smolić
2024-03-03 9:26 Jakov Smolić
2024-02-01 14:44 Petr Vaněk
2024-01-22 8:18 Petr Vaněk
2024-01-21 2:51 Sam James
2024-01-21 2:44 Sam James
2024-01-21 2:44 Sam James
2024-01-17 10:39 Petr Vaněk
2023-12-21 14:47 Petr Vaněk
2023-12-21 14:28 Petr Vaněk
2023-12-21 6:12 Joonas Niilola
2023-12-21 6:12 Joonas Niilola
2023-11-22 11:38 Sam James
2023-11-20 10:06 Sam James
2023-11-17 11:09 Sam James
2023-07-15 8:01 Joonas Niilola
2023-05-20 12:32 Joonas Niilola
2023-05-16 5:58 Joonas Niilola
2023-05-16 5:58 Joonas Niilola
2023-05-06 9:49 Arthur Zamarin
2023-04-15 12:23 Joonas Niilola
2023-04-15 12:23 Joonas Niilola
2023-03-30 5:22 Joonas Niilola
2023-03-25 5:13 Arthur Zamarin
2023-02-21 8:01 Sam James
2023-02-16 22:07 Yixun Lan
2023-01-20 1:23 Sam James
2023-01-17 1:53 Sam James
2023-01-17 1:53 Sam James
2022-08-16 15:26 Joonas Niilola
2022-08-02 5:40 Joonas Niilola
2022-08-02 5:40 Joonas Niilola
2022-06-25 5:36 Sam James
2022-05-24 7:01 Joonas Niilola
2022-05-22 6:06 Joonas Niilola
2022-05-22 6:06 Joonas Niilola
2022-04-24 9:49 Joonas Niilola
2022-03-12 9:46 Arthur Zamarin
2022-03-11 8:31 Joonas Niilola
2022-03-10 9:48 Jakov Smolić
2021-12-16 17:19 Jakov Smolić
2021-12-16 17:12 Jakov Smolić
2021-12-16 16:39 Jakov Smolić
2020-10-11 17:49 William Hubbs
2020-05-16 7:09 Joonas Niilola
2019-11-28 21:54 William Hubbs
2019-06-22 7:52 Michał Górny
2018-10-09 0:11 Georgy Yakovlev
2018-10-02 22:08 Michał Górny
2018-05-31 22:48 William Hubbs
2018-03-29 13:25 William Hubbs
2018-01-10 21:35 William Hubbs
2017-11-15 20:15 William Hubbs
2017-10-03 18:47 William Hubbs
2017-05-22 16:00 William Hubbs
2017-05-21 21:29 William Hubbs
2017-05-05 19:43 Markus Meier
2017-04-26 21:29 William Hubbs
2017-01-11 23:43 William Hubbs
2016-06-29 17:45 William Hubbs
2016-01-13 22:25 William Hubbs
2015-08-09 18:27 Mikle Kolyada
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=1705459496.03e543773c7377b83b4cd4433ddb777926078451.ionen@gentoo \
--to=ionen@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