public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-apps/s6/
Date: Mon, 15 Jul 2024 11:49:14 +0000 (UTC)	[thread overview]
Message-ID: <1721044091.0416c882c078a933d05b415514660004922f5f3c.sam@gentoo> (raw)

commit:     0416c882c078a933d05b415514660004922f5f3c
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Mon Jul 15 11:48:11 2024 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Mon Jul 15 11:48:11 2024 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=0416c882

sys-apps/s6: Stabilize 2.13.0.0 x86, #936090

Signed-off-by: Sam James <sam <AT> gentoo.org>

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

diff --git a/sys-apps/s6/s6-2.13.0.0.ebuild b/sys-apps/s6/s6-2.13.0.0.ebuild
index 75a6f7ec08d5..5afec8c9ea5d 100644
--- a/sys-apps/s6/s6-2.13.0.0.ebuild
+++ b/sys-apps/s6/s6-2.13.0.0.ebuild
@@ -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 ~mips ~ppc ~ppc64 ~riscv ~x86"
+KEYWORDS="~alpha ~amd64 ~arm ~mips ~ppc ~ppc64 ~riscv x86"
 IUSE="+execline"
 
 RDEPEND="


             reply	other threads:[~2024-07-15 11:49 UTC|newest]

Thread overview: 78+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-15 11:49 Sam James [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/ Petr Vaněk
2024-08-30 10:19 Petr Vaněk
2024-07-15 11:50 Sam James
2024-07-15 11:49 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-05-26 20:28 Petr Vaněk
2024-05-19 14:51 Sam James
2024-05-19 13:58 Sam James
2024-05-19 13:58 Sam James
2024-04-17  8:01 Petr Vaněk
2024-01-22  8:18 Petr Vaněk
2024-01-21  4:29 Sam James
2024-01-21  4:29 Sam James
2024-01-21  4:29 Sam James
2024-01-17 10:39 Petr Vaněk
2024-01-17  2:46 Ionen Wolkens
2023-12-21 14:28 Petr Vaněk
2023-12-21 14:28 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-12-05 15:08 Petr Vaněk
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-17  1:53 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-30 21:41 Sam James
2022-06-25  5:36 Sam James
2022-06-13 14:56 Joonas Niilola
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-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 21:43 William Hubbs
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-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-03-07 22:51 William Hubbs
2016-03-07 22:51 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=1721044091.0416c882c078a933d05b415514660004922f5f3c.sam@gentoo \
    --to=sam@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