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-process/fcron/
Date: Sun, 12 May 2024 22:41:18 +0000 (UTC)	[thread overview]
Message-ID: <1715553632.87ec0643358594138884a59733eb393755161bf7.sam@gentoo> (raw)

commit:     87ec0643358594138884a59733eb393755161bf7
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sun May 12 22:40:32 2024 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sun May 12 22:40:32 2024 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=87ec0643

sys-process/fcron: Stabilize 3.3.1-r1 ppc64, #931790

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

 sys-process/fcron/fcron-3.3.1-r1.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/sys-process/fcron/fcron-3.3.1-r1.ebuild b/sys-process/fcron/fcron-3.3.1-r1.ebuild
index f2eebae9a3e5..73a278f4d605 100644
--- a/sys-process/fcron/fcron-3.3.1-r1.ebuild
+++ b/sys-process/fcron/fcron-3.3.1-r1.ebuild
@@ -17,7 +17,7 @@ S="${WORKDIR}/${MY_P}"
 
 LICENSE="GPL-2"
 SLOT="0"
-KEYWORDS="~amd64 arm ~arm64 ~hppa ~ia64 ~loong ~mips ppc ~ppc64 ~riscv sparc ~x86"
+KEYWORDS="~amd64 arm ~arm64 ~hppa ~ia64 ~loong ~mips ppc ppc64 ~riscv sparc ~x86"
 IUSE="audit debug pam selinux l10n_fr +mta +system-crontab readline"
 
 DEPEND="


             reply	other threads:[~2024-05-12 22:41 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-12 22:41 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-08-30 14:23 [gentoo-commits] repo/gentoo:master commit in: sys-process/fcron/ Arthur Zamarin
2024-05-13  5:27 Joonas Niilola
2024-05-13  5:27 Joonas Niilola
2024-05-12 22:41 Sam James
2024-05-12 22:41 Sam James
2024-05-12 22:41 Sam James
2024-03-09 10:46 Florian Schmaus
2023-03-11 23:35 David Seifert
2023-02-27  9:04 Joonas Niilola
2023-02-26 19:25 Sam James
2023-02-24 10:01 Sam James
2023-02-24  9:29 Sam James
2023-02-24  9:29 Sam James
2023-02-24  9:29 Sam James
2023-02-24  9:29 Sam James
2023-02-23  7:04 Joonas Niilola
2022-08-28  6:30 WANG Xuerui
2022-05-14 11:48 Anthony G. Basile
2022-02-13  0:56 Conrad Kostecki
2022-01-19 18:32 Anthony G. Basile
2021-12-30 20:40 Arthur Zamarin
2021-12-28  5:57 Sam James
2021-12-27 14:13 Agostino Sarubbo
2021-12-26 18:57 Arthur Zamarin
2021-12-26 18:54 Arthur Zamarin
2021-12-26 18:49 Arthur Zamarin
2021-12-02  8:29 Andreas Sturmlechner
2021-11-16  6:13 Sam James
2021-10-20 10:33 Sam James
2021-10-20  7:30 Sam James
2021-10-19 20:26 Anthony G. Basile
2021-08-05  2:49 Yixun Lan
2021-07-21  2:22 Yixun Lan
2021-06-25 19:32 Sam James
2021-02-24 21:03 Sam James
2021-01-22 21:19 Sam James
2020-12-22 16:29 Thomas Deutschmann
2020-10-28 16:44 Sam James
2019-10-12 18:17 Mikle Kolyada
2017-12-20 17:41 Anthony G. Basile
2017-11-26 23:26 David Seifert
2017-06-09 10:54 Thomas Deutschmann
2017-03-08  5:30 Jeroen Roovers
2017-02-18 18:59 Markus Meier
2017-01-11 11:34 Aaron Bauman
2016-11-17 22:00 Thomas Deutschmann
2016-08-07  9:30 Pacho Ramos
2016-06-25 15:57 Ulrich Müller
2016-05-19 17:48 Mike Frysinger
2016-01-02  3:16 Anthony G. Basile
2016-01-02  3:05 Anthony G. Basile

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=1715553632.87ec0643358594138884a59733eb393755161bf7.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