From: "Ionen Wolkens" <ionen@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-apps/s6-linux-utils/
Date: Wed, 17 Jan 2024 02:46:04 +0000 (UTC) [thread overview]
Message-ID: <1705459497.249d1fa3b1c966d16357309c57b2d04af39d4d5e.ionen@gentoo> (raw)
commit: 249d1fa3b1c966d16357309c57b2d04af39d4d5e
Author: Matoro Mahri <matoro_gentoo <AT> matoro <DOT> tk>
AuthorDate: Tue Jan 16 20:30:48 2024 +0000
Commit: Ionen Wolkens <ionen <AT> gentoo <DOT> org>
CommitDate: Wed Jan 17 02:44:57 2024 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=249d1fa3
sys-apps/s6-linux-utils: Stabilize 2.6.2.0 arm, #920377
Signed-off-by: Matoro Mahri <matoro_gentoo <AT> matoro.tk>
Signed-off-by: Ionen Wolkens <ionen <AT> gentoo.org>
sys-apps/s6-linux-utils/s6-linux-utils-2.6.2.0.ebuild | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/sys-apps/s6-linux-utils/s6-linux-utils-2.6.2.0.ebuild b/sys-apps/s6-linux-utils/s6-linux-utils-2.6.2.0.ebuild
index ba5d70f74e27..1a6996910b2b 100644
--- a/sys-apps/s6-linux-utils/s6-linux-utils-2.6.2.0.ebuild
+++ b/sys-apps/s6-linux-utils/s6-linux-utils-2.6.2.0.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"
-KEYWORDS="amd64 ~arm ~arm64 x86"
+KEYWORDS="amd64 arm ~arm64 x86"
RDEPEND=">=dev-libs/skalibs-2.13.0.0:="
DEPEND="${RDEPEND}"
next reply other threads:[~2024-01-17 2:46 UTC|newest]
Thread overview: 48+ 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-01-17 10:39 [gentoo-commits] repo/gentoo:master commit in: sys-apps/s6-linux-utils/ Petr Vaněk
2023-12-21 6:12 Joonas Niilola
2023-12-21 6:12 Joonas Niilola
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-03-30 5:22 Joonas Niilola
2023-03-28 14:59 Sam James
2023-03-25 5:13 Arthur Zamarin
2023-03-07 7:49 Joonas Niilola
2023-02-24 15:09 Joonas Niilola
2023-02-21 8:01 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-06-25 5:36 Sam James
2022-05-24 7:01 Joonas Niilola
2022-04-24 9:49 Joonas Niilola
2022-03-12 9:46 Arthur Zamarin
2022-03-10 9:48 Jakov Smolić
2022-01-28 8:00 Sam James
2022-01-28 8:00 Sam James
2022-01-28 8:00 Sam James
2022-01-28 8:00 Sam James
2020-10-11 17:49 William Hubbs
2020-07-15 12:30 Sam James
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:12 Georgy Yakovlev
2018-10-02 22:08 Michał Górny
2018-03-29 13:25 William Hubbs
2017-11-15 20:15 William Hubbs
2017-10-03 18:47 William Hubbs
2017-05-21 21:29 William Hubbs
2017-04-26 21:29 William Hubbs
2017-01-11 23:43 William Hubbs
2016-06-29 17:45 William Hubbs
2016-04-13 16:35 William Hubbs
2016-02-04 18:30 Kristian Fiskerstrand
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=1705459497.249d1fa3b1c966d16357309c57b2d04af39d4d5e.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