From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-analyzer/nagios-check_mysql_health/
Date: Thu, 23 May 2024 21:53:55 +0000 (UTC) [thread overview]
Message-ID: <1716501204.8af4a43dfba5db8f67cf786ed526302f9e5164cd.sam@gentoo> (raw)
commit: 8af4a43dfba5db8f67cf786ed526302f9e5164cd
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Thu May 23 21:53:24 2024 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Thu May 23 21:53:24 2024 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=8af4a43d
net-analyzer/nagios-check_mysql_health: Stabilize 2.2.2-r1 x86, #932231
Signed-off-by: Sam James <sam <AT> gentoo.org>
.../nagios-check_mysql_health/nagios-check_mysql_health-2.2.2-r1.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/net-analyzer/nagios-check_mysql_health/nagios-check_mysql_health-2.2.2-r1.ebuild b/net-analyzer/nagios-check_mysql_health/nagios-check_mysql_health-2.2.2-r1.ebuild
index eb91aed60971..666eecff017a 100644
--- a/net-analyzer/nagios-check_mysql_health/nagios-check_mysql_health-2.2.2-r1.ebuild
+++ b/net-analyzer/nagios-check_mysql_health/nagios-check_mysql_health-2.2.2-r1.ebuild
@@ -13,7 +13,7 @@ S="${WORKDIR}/${MY_P}"
LICENSE="BSD"
SLOT="0"
-KEYWORDS="amd64 ~x86"
+KEYWORDS="amd64 x86"
# Found by grepping for "use " in the built
# plugins-scripts/check_mysql_health.
next reply other threads:[~2024-05-23 21:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-23 21:53 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-05-24 10:07 [gentoo-commits] repo/gentoo:master commit in: net-analyzer/nagios-check_mysql_health/ Arthur Zamarin
2024-05-23 21:53 Sam James
2024-04-16 1:15 Michael Orlitzky
2020-02-08 18:55 David Seifert
2019-03-02 21:35 Michael Orlitzky
2019-03-02 20:49 Thomas Deutschmann
2019-02-28 14:19 Mikle Kolyada
2016-08-09 4:43 Michael Orlitzky
2016-08-09 4:29 Michael Orlitzky
2016-08-07 8:36 Pacho Ramos
2015-08-26 11:00 Agostino Sarubbo
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=1716501204.8af4a43dfba5db8f67cf786ed526302f9e5164cd.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