public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Thomas Deutschmann" <whissi@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/progressbar2/
Date: Thu,  1 Apr 2021 12:54:09 +0000 (UTC)	[thread overview]
Message-ID: <1617281616.449c32ac5084c65655d2bf6dabd92112e51cad3b.whissi@gentoo> (raw)

commit:     449c32ac5084c65655d2bf6dabd92112e51cad3b
Author:     Thomas Deutschmann <whissi <AT> gentoo <DOT> org>
AuthorDate: Thu Apr  1 12:53:36 2021 +0000
Commit:     Thomas Deutschmann <whissi <AT> gentoo <DOT> org>
CommitDate: Thu Apr  1 12:53:36 2021 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=449c32ac

dev-python/progressbar2: x86 keyworded (bug #733826)

Package-Manager: Portage-3.0.18, Repoman-3.0.3
Signed-off-by: Thomas Deutschmann <whissi <AT> gentoo.org>

 dev-python/progressbar2/progressbar2-3.53.1.ebuild | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/dev-python/progressbar2/progressbar2-3.53.1.ebuild b/dev-python/progressbar2/progressbar2-3.53.1.ebuild
index 987ee7125a5..dc065e44f01 100644
--- a/dev-python/progressbar2/progressbar2-3.53.1.ebuild
+++ b/dev-python/progressbar2/progressbar2-3.53.1.ebuild
@@ -1,4 +1,4 @@
-# Copyright 1999-2020 Gentoo Authors
+# Copyright 1999-2021 Gentoo Authors
 # Distributed under the terms of the GNU General Public License v2
 
 EAPI=7
@@ -12,7 +12,7 @@ SRC_URI="mirror://pypi/${PN:0:1}/${PN}/${P}.tar.gz"
 
 LICENSE="BSD"
 SLOT="0"
-KEYWORDS="amd64"
+KEYWORDS="amd64 ~x86"
 
 CDEPEND="!dev-python/progressbar[${PYTHON_USEDEP}]
 	dev-python/python-utils[${PYTHON_USEDEP}]"


             reply	other threads:[~2021-04-01 12:54 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-01 12:54 Thomas Deutschmann [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-03-12 12:49 [gentoo-commits] repo/gentoo:master commit in: dev-python/progressbar2/ Michał Górny
2024-09-14 12:32 Michał Górny
2024-09-14 12:06 Arthur Zamarin
2024-08-29  4:52 Michał Górny
2024-07-08 19:22 Michał Górny
2024-03-22  4:38 Michał Górny
2024-03-21 19:24 Arthur Zamarin
2024-03-16 12:08 Michał Górny
2024-03-16 11:21 Arthur Zamarin
2024-03-05 19:11 Michał Górny
2024-02-26  4:35 Michał Górny
2024-01-06  9:54 Michał Górny
2024-01-06  9:50 Michał Górny
2023-12-18 17:07 Michał Górny
2023-11-24 16:32 Arthur Zamarin
2023-11-23 20:20 Michał Górny
2023-06-03 17:45 Michał Górny
2022-11-19 16:54 Michał Górny
2022-11-19 16:40 Sam James
2022-10-26 18:42 Arthur Zamarin
2022-10-18 18:07 Arthur Zamarin
2022-08-10 13:05 Sam James
2022-06-05  5:36 Michał Górny
2022-02-13 10:38 Michał Górny
2022-02-13 10:27 Jakov Smolić
2022-01-05 17:18 Arthur Zamarin
2021-11-13 13:22 Michał Górny
2021-11-13 11:35 Jakov Smolić
2021-10-16  6:09 Michał Górny
2021-10-16  1:14 Sam James
2021-10-15 21:07 Michał Górny
2021-10-13  9:05 Michał Górny
2021-10-04 20:40 Sam James
2021-09-15 20:26 Michał Górny
2021-08-25 17:40 Arthur Zamarin
2021-08-25 17:40 Arthur Zamarin
2021-08-25 17:40 Arthur Zamarin
2020-12-16 11:12 Sam James
2020-12-03 14:49 Sam James
2020-12-03 11:10 Sam James
2020-12-03  8:43 Sam James
2020-01-18 18:48 Michał Górny
2019-05-22 14:48 Tony Vroon
2019-02-01 15:52 Tony Vroon

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=1617281616.449c32ac5084c65655d2bf6dabd92112e51cad3b.whissi@gentoo \
    --to=whissi@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