From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-portage/portpeek/
Date: Fri, 12 Mar 2021 15:25:21 +0000 (UTC) [thread overview]
Message-ID: <1615562712.b86b2c39ea2c1b9948c0fca798d0d529bb0a8bf4.sam@gentoo> (raw)
commit: b86b2c39ea2c1b9948c0fca798d0d529bb0a8bf4
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Fri Mar 12 15:23:58 2021 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Fri Mar 12 15:25:12 2021 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b86b2c39
app-portage/portpeek: Stabilize 3.2.0 ALLARCHES, #775506
Signed-off-by: Sam James <sam <AT> gentoo.org>
app-portage/portpeek/portpeek-3.2.0.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/app-portage/portpeek/portpeek-3.2.0.ebuild b/app-portage/portpeek/portpeek-3.2.0.ebuild
index f37447bf07d..2ee5d4b9bb1 100644
--- a/app-portage/portpeek/portpeek-3.2.0.ebuild
+++ b/app-portage/portpeek/portpeek-3.2.0.ebuild
@@ -12,7 +12,7 @@ SRC_URI="https://www.mpagano.com/downloads/${P}.tar.gz"
LICENSE="GPL-2"
SLOT="0"
-KEYWORDS="~amd64 ~arm ~arm64 ~ppc ~sparc ~x86"
+KEYWORDS="amd64 arm arm64 ppc sparc x86"
IUSE=""
REQUIRED_USE="${PYTHON_REQUIRED_USE}"
next reply other threads:[~2021-03-12 15:25 UTC|newest]
Thread overview: 83+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-12 15:25 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-09-23 17:46 [gentoo-commits] repo/gentoo:master commit in: app-portage/portpeek/ Mike Pagano
2024-09-14 22:21 Mike Pagano
2024-08-18 1:12 Michael Orlitzky
2024-07-14 22:07 Mike Pagano
2023-12-29 13:07 Mike Pagano
2023-12-14 15:31 Mike Pagano
2023-12-14 15:31 Mike Pagano
2023-12-13 14:01 Mike Pagano
2023-11-01 17:16 Mike Pagano
2023-10-17 18:07 Mike Pagano
2022-12-03 19:48 Mike Pagano
2022-12-03 19:48 Mike Pagano
2022-12-03 19:38 Mike Pagano
2022-10-31 12:44 Mike Pagano
2022-08-08 19:59 Jakov Smolić
2022-07-31 16:08 Jakov Smolić
2022-07-11 18:03 Mike Pagano
2022-05-09 20:16 Mike Pagano
2022-01-30 23:56 Mike Pagano
2022-01-26 14:23 Mike Pagano
2021-11-25 14:44 Mike Pagano
2021-11-14 23:17 Mike Pagano
2021-11-11 21:14 Jakov Smolić
2021-08-12 18:48 Mike Pagano
2021-06-11 18:57 Mike Pagano
2021-03-14 0:33 Mike Pagano
2021-01-24 17:28 Mike Pagano
2020-11-12 14:13 Mike Pagano
2020-11-11 16:16 Sam James
2020-10-07 17:26 Mike Pagano
2020-09-08 10:57 Mike Pagano
2020-09-03 22:26 Mike Pagano
2020-09-02 22:54 Sam James
2020-09-02 22:52 Sam James
2020-09-02 22:51 Sam James
2020-09-02 22:50 Sam James
2020-09-02 19:37 Sam James
2020-08-28 20:56 Mike Pagano
2020-07-30 12:40 Mike Pagano
2020-07-24 19:40 Mike Pagano
2020-07-23 18:12 Mike Pagano
2020-07-20 23:30 Mike Pagano
2020-07-20 21:06 Mike Pagano
2020-05-20 18:31 Mike Pagano
2020-05-08 6:25 Mart Raudsepp
2020-04-26 17:27 Mike Pagano
2020-04-23 6:29 Agostino Sarubbo
2020-04-23 6:28 Agostino Sarubbo
2020-04-23 6:24 Agostino Sarubbo
2020-04-23 6:21 Agostino Sarubbo
2020-04-22 17:01 Agostino Sarubbo
2020-02-08 20:48 Mike Pagano
2020-01-16 13:32 Mike Pagano
2019-08-01 16:00 Mike Pagano
2019-07-30 11:27 Mike Pagano
2019-07-29 18:33 Matt Turner
2019-07-28 11:03 Mikle Kolyada
2019-05-20 11:21 Mikle Kolyada
2019-05-13 1:41 Thomas Deutschmann
2019-04-29 8:49 Sergei Trofimovich
2019-04-24 16:33 Mike Pagano
2018-08-06 13:32 Mike Pagano
2018-08-02 16:02 Mike Pagano
2018-03-21 22:13 Mike Pagano
2018-03-21 18:12 Michał Górny
2018-03-20 9:13 Sergei Trofimovich
2018-03-15 16:06 Mikle Kolyada
2018-02-13 17:26 Mike Pagano
2018-02-05 13:00 Mike Pagano
2018-01-17 6:42 Thomas Deutschmann
2018-01-17 0:19 Mike Pagano
2017-09-19 11:49 Mike Pagano
2017-09-17 23:46 Mike Pagano
2017-04-20 13:11 Mike Pagano
2017-02-27 20:17 Mike Pagano
2017-02-20 18:06 Markus Meier
2017-01-25 23:23 Mike Pagano
2017-01-17 13:26 Aaron Bauman
2016-12-05 23:30 Mike Pagano
2016-12-04 21:13 Mike Pagano
2016-08-08 14:36 Mike Pagano
2016-01-12 18:30 Mike Pagano
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=1615562712.b86b2c39ea2c1b9948c0fca798d0d529bb0a8bf4.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