From: "Agostino Sarubbo" <ago@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/bitstring/
Date: Thu, 26 Aug 2021 04:41:15 +0000 (UTC) [thread overview]
Message-ID: <1629952826.ef00f098171988b8c1dcafef5c220ecd6ab228c2.ago@gentoo> (raw)
commit: ef00f098171988b8c1dcafef5c220ecd6ab228c2
Author: Agostino Sarubbo <ago <AT> gentoo <DOT> org>
AuthorDate: Thu Aug 26 04:40:26 2021 +0000
Commit: Agostino Sarubbo <ago <AT> gentoo <DOT> org>
CommitDate: Thu Aug 26 04:40:26 2021 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ef00f098
dev-python/bitstring: amd64/x86 stable (ALLARCHES policy) wrt bug #810363
Package-Manager: Portage-3.0.20, Repoman-3.0.2
Signed-off-by: Agostino Sarubbo <ago <AT> gentoo.org>
dev-python/bitstring/bitstring-3.1.9.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-python/bitstring/bitstring-3.1.9.ebuild b/dev-python/bitstring/bitstring-3.1.9.ebuild
index 6e59803ccaf..eedb23302ce 100644
--- a/dev-python/bitstring/bitstring-3.1.9.ebuild
+++ b/dev-python/bitstring/bitstring-3.1.9.ebuild
@@ -13,7 +13,7 @@ S=${WORKDIR}/${PN}-${P}
LICENSE="MIT"
SLOT="0"
-KEYWORDS="~amd64 ~arm ~arm64 ~x86"
+KEYWORDS="amd64 ~arm ~arm64 x86"
distutils_enable_tests unittest
next reply other threads:[~2021-08-26 4:41 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-26 4:41 Agostino Sarubbo [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-04-12 7:40 [gentoo-commits] repo/gentoo:master commit in: dev-python/bitstring/ Michał Górny
2025-03-23 3:41 Michał Górny
2025-03-18 19:30 Michał Górny
2025-01-18 8:28 Michał Górny
2025-01-18 8:24 Michał Górny
2025-01-02 4:54 Michał Górny
2024-06-29 16:58 Michał Górny
2024-06-12 6:17 Arthur Zamarin
2024-06-12 6:16 Arthur Zamarin
2024-06-10 14:41 Michał Górny
2024-05-26 2:54 Michał Górny
2024-05-16 15:00 Arthur Zamarin
2024-05-11 5:19 Michał Górny
2024-05-08 8:51 Michał Górny
2024-05-08 8:51 Michał Górny
2024-04-25 4:43 Michał Górny
2024-04-23 7:04 Michał Górny
2024-04-22 15:29 Michał Górny
2023-12-15 10:59 Michał Górny
2023-12-15 10:50 Arthur Zamarin
2023-12-02 9:50 Michał Górny
2023-12-02 9:34 Michał Górny
2023-11-30 5:48 Michał Górny
2023-11-24 14:46 Michał Górny
2023-11-23 4:19 Michał Górny
2023-11-17 11:40 Andrey Grozin
2023-09-25 18:52 Michał Górny
2023-09-25 17:33 Arthur Zamarin
2023-08-23 19:25 Michał Górny
2023-08-18 1:29 Sam James
2023-08-18 1:29 Sam James
2023-08-17 18:55 Michał Górny
2023-05-23 16:15 Michał Górny
2023-05-23 15:53 Arthur Zamarin
2023-04-17 5:41 Michał Górny
2023-03-11 9:53 Michał Górny
2023-03-11 8:34 Arthur Zamarin
2023-02-02 14:48 Michał Górny
2022-05-12 19:21 Arthur Zamarin
2021-08-26 8:24 Michał Górny
2021-07-21 7:25 Michał Górny
2021-07-20 20:47 Michał Górny
2021-07-18 6:16 Michał Górny
2021-06-05 12:56 Michał Górny
2020-12-12 4:27 Sam James
2020-09-18 14:28 Michał Górny
2020-09-08 19:11 Michał Górny
2020-07-20 14:40 Michał Górny
2020-07-20 14:40 Michał Górny
2020-05-11 16:48 Michał Górny
2020-05-11 9:44 Agostino Sarubbo
2020-02-29 10:50 Andrey Grozin
2020-02-04 13:32 Michał Górny
2019-05-20 6:33 Stephen Klimaszewski
2017-05-15 13:04 Manuel Rüger
2016-11-07 2:14 Andrey Grozin
2016-11-06 13:17 Michael Palimaka
2016-11-06 13:17 Michael Palimaka
2016-06-06 21:15 Tim Harder
2016-06-06 21:12 Tim Harder
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=1629952826.ef00f098171988b8c1dcafef5c220ecd6ab228c2.ago@gentoo \
--to=ago@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