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: app-admin/setools/
Date: Wed, 28 Jul 2021 20:08:03 +0000 (UTC)	[thread overview]
Message-ID: <1627502865.2a4dbd9df2f01820155d8bb028fba6cd4389b661.sam@gentoo> (raw)

commit:     2a4dbd9df2f01820155d8bb028fba6cd4389b661
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Wed Jul 28 20:04:40 2021 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Wed Jul 28 20:07:45 2021 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=2a4dbd9d

app-admin/setools: Stabilize 4.4.0 x86, #797616

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

 app-admin/setools/setools-4.4.0.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/app-admin/setools/setools-4.4.0.ebuild b/app-admin/setools/setools-4.4.0.ebuild
index bab448134a7..fccf62f2369 100644
--- a/app-admin/setools/setools-4.4.0.ebuild
+++ b/app-admin/setools/setools-4.4.0.ebuild
@@ -15,7 +15,7 @@ if [[ ${PV} == 9999 ]] ; then
 	EGIT_REPO_URI="https://github.com/SELinuxProject/setools.git"
 else
 	SRC_URI="https://github.com/SELinuxProject/setools/releases/download/${PV}/${P}.tar.bz2"
-	KEYWORDS="amd64 ~arm ~arm64 ~x86"
+	KEYWORDS="amd64 ~arm ~arm64 x86"
 fi
 
 LICENSE="GPL-2 LGPL-2.1"


             reply	other threads:[~2021-07-28 20:08 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-28 20:08 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-07-19 19:50 [gentoo-commits] repo/gentoo:master commit in: app-admin/setools/ Jakov Smolić
2024-07-19 16:36 Jakov Smolić
2024-05-05 20:52 Jason Zaman
2024-02-09 14:41 Kenton Groombridge
2024-01-17  1:33 Kenton Groombridge
2024-01-17  1:33 Kenton Groombridge
2023-09-24 16:16 Kenton Groombridge
2023-07-27  7:18 Sam James
2023-07-27  7:07 Sam James
2023-07-27  7:07 Sam James
2023-03-30  0:09 Kenton Groombridge
2022-04-12  1:37 Jason Zaman
2022-04-11  3:44 Jason Zaman
2021-11-20 23:20 Sam James
2021-11-20 23:20 Sam James
2021-11-20 15:00 Sam James
2021-09-19  6:48 Sam James
2021-09-19  6:30 Sam James
2021-07-04 22:19 Sam James
2021-04-03  4:19 Jason Zaman
2021-01-03  8:20 Jason Zaman
2020-12-03  3:12 Jason Zaman
2020-08-13 20:25 Michał Górny
2020-02-15 13:21 Jason Zaman
2020-02-15 13:21 Jason Zaman
2019-12-08 18:39 Jason Zaman
2019-08-17 10:09 Jason Zaman
2019-08-17 10:09 Jason Zaman
2019-08-17 10:09 Jason Zaman
2019-02-09 11:49 Jason Zaman
2018-12-27 11:26 Jason Zaman
2018-08-12 15:38 Virgil Dupras
2018-05-28  9:32 Jason Zaman
2018-05-25  7:58 Jason Zaman
2018-05-25  7:58 Jason Zaman
2018-03-03 18:38 Michał Górny
2018-03-02  6:27 Jason Zaman
2017-12-06 13:33 Jason Zaman
2017-09-23  2:15 Jason Zaman
2017-09-23  2:15 Jason Zaman
2017-08-07 16:48 Jason Zaman
2017-08-07 16:48 Jason Zaman
2017-04-23  4:28 Jason Zaman
2017-04-23  4:04 Jason Zaman
2017-04-19  8:03 David Seifert
2017-04-10 18:39 Sven Vermeulen
2017-02-01 17:23 Sven Vermeulen
2017-02-01 17:23 Sven Vermeulen
2017-02-01 17:18 Sven Vermeulen
2016-12-12 14:01 Jason Zaman
2016-10-03  7:30 Jason Zaman
2016-09-01 16:31 Jason Zaman
2016-06-22  6:43 Patrice Clement
2016-06-01 13:19 Jason Zaman
2015-12-21  8:57 Jason Zaman

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=1627502865.2a4dbd9df2f01820155d8bb028fba6cd4389b661.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