From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-cluster/slurm/
Date: Wed, 2 Feb 2022 05:30:39 +0000 (UTC) [thread overview]
Message-ID: <1643779821.e68e99f2a0ef13a3b4c265f2287385d7e835e350.sam@gentoo> (raw)
commit: e68e99f2a0ef13a3b4c265f2287385d7e835e350
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Wed Feb 2 05:30:21 2022 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Wed Feb 2 05:30:21 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e68e99f2
sys-cluster/slurm: Stabilize 20.11.0.1-r104 amd64, #816579
Signed-off-by: Sam James <sam <AT> gentoo.org>
sys-cluster/slurm/slurm-20.11.0.1-r104.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/sys-cluster/slurm/slurm-20.11.0.1-r104.ebuild b/sys-cluster/slurm/slurm-20.11.0.1-r104.ebuild
index 378b082b71ea..7e9988bd49b4 100644
--- a/sys-cluster/slurm/slurm-20.11.0.1-r104.ebuild
+++ b/sys-cluster/slurm/slurm-20.11.0.1-r104.ebuild
@@ -18,7 +18,7 @@ else
MY_P="${PN}-${MY_PV}"
INHERIT_GIT=""
SRC_URI="https://github.com/SchedMD/slurm/archive/${MY_P}.tar.gz"
- KEYWORDS="~amd64 ~riscv ~x86"
+ KEYWORDS="amd64 ~riscv ~x86"
fi
inherit autotools bash-completion-r1 lua-single pam perl-module prefix toolchain-funcs systemd ${INHERIT_GIT} tmpfiles
next reply other threads:[~2022-02-02 5:30 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-02 5:30 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-18 13:47 [gentoo-commits] repo/gentoo:master commit in: sys-cluster/slurm/ Benda XU
2024-10-18 13:47 Benda XU
2024-10-18 13:47 Benda XU
2022-10-27 4:48 Sam James
2022-10-06 11:14 Joonas Niilola
2022-09-15 8:06 Alexey Shvetsov
2022-07-09 8:38 David Seifert
2022-06-26 7:02 Sam James
2022-02-02 6:21 Sam James
2022-01-16 18:47 David Seifert
2021-10-29 22:44 Sam James
2021-10-12 7:06 Sam James
2021-07-30 23:31 Sam James
2021-07-05 19:38 Marek Szuba
2021-07-05 19:38 Marek Szuba
2021-03-25 23:31 Conrad Kostecki
2021-03-13 17:24 David Seifert
2021-03-07 11:58 David Seifert
2021-01-05 15:17 Mikle Kolyada
2020-12-01 12:16 Mikle Kolyada
2020-12-01 12:13 Mikle Kolyada
2020-09-20 13:07 Mikle Kolyada
2020-09-20 13:07 Mikle Kolyada
2020-08-29 10:10 Mikle Kolyada
2020-07-26 1:53 Thomas Deutschmann
2020-06-07 10:54 Mikle Kolyada
2020-05-25 20:47 Alexey Shvetsov
2020-05-25 19:46 Alexey Shvetsov
2020-05-22 10:39 Mikle Kolyada
2020-05-22 10:38 Mikle Kolyada
2020-05-14 14:21 Mikle Kolyada
2020-05-14 14:21 Mikle Kolyada
2020-03-27 13:30 Mikle Kolyada
2020-03-27 13:23 Mikle Kolyada
2020-02-29 13:00 Mikle Kolyada
2019-12-21 11:11 Mikle Kolyada
2019-12-21 9:46 Mikle Kolyada
2019-12-21 9:05 Mikle Kolyada
2019-12-21 8:59 Mikle Kolyada
2019-12-21 8:25 Mikle Kolyada
2019-12-01 8:56 Mikle Kolyada
2019-11-15 15:04 Mikle Kolyada
2019-10-20 20:27 Mikle Kolyada
2019-10-20 19:35 Mikle Kolyada
2019-10-20 18:35 Mikle Kolyada
2019-10-20 17:26 Mikle Kolyada
2019-10-20 16:50 Mikle Kolyada
2019-10-12 18:40 Mikle Kolyada
2019-10-06 18:07 Mikle Kolyada
2018-10-27 12:15 Justin Lecher
2018-06-10 9:41 Justin Lecher
2017-11-26 17:17 Justin Lecher
2017-11-26 17:17 Justin Lecher
2017-11-12 19:56 Justin Lecher
2017-07-30 9:23 Michał Górny
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=1643779821.e68e99f2a0ef13a3b4c265f2287385d7e835e350.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