public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Joonas Niilola" <juippis@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-apps/s6-linux-utils/
Date: Tue, 16 May 2023 05:58:08 +0000 (UTC)	[thread overview]
Message-ID: <1684216684.a5667e689e0257ebac7a49b51b8f46066f4b961c.juippis@gentoo> (raw)

commit:     a5667e689e0257ebac7a49b51b8f46066f4b961c
Author:     Joonas Niilola <juippis <AT> gentoo <DOT> org>
AuthorDate: Tue May 16 05:56:10 2023 +0000
Commit:     Joonas Niilola <juippis <AT> gentoo <DOT> org>
CommitDate: Tue May 16 05:58:04 2023 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a5667e68

sys-apps/s6-linux-utils: Stabilize 2.6.1.2 amd64, #906462

Signed-off-by: Joonas Niilola <juippis <AT> gentoo.org>

 sys-apps/s6-linux-utils/s6-linux-utils-2.6.1.2.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/sys-apps/s6-linux-utils/s6-linux-utils-2.6.1.2.ebuild b/sys-apps/s6-linux-utils/s6-linux-utils-2.6.1.2.ebuild
index 43ea27b14a6a..1769e60ef6d6 100644
--- a/sys-apps/s6-linux-utils/s6-linux-utils-2.6.1.2.ebuild
+++ b/sys-apps/s6-linux-utils/s6-linux-utils-2.6.1.2.ebuild
@@ -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}"


             reply	other threads:[~2023-05-16  5:58 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-16  5:58 Joonas Niilola [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-10-24  9:39 [gentoo-commits] repo/gentoo:master commit in: sys-apps/s6-linux-utils/ Petr Vaněk
2024-01-17 10:39 Petr Vaněk
2024-01-17  2:46 Ionen Wolkens
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-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=1684216684.a5667e689e0257ebac7a49b51b8f46066f4b961c.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