public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Agostino Sarubbo" <ago@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/cx_Freeze/
Date: Fri, 26 Feb 2021 12:07:27 +0000 (UTC)	[thread overview]
Message-ID: <1614341228.53fcfbbc7e3c640717814bf93e2aaa283ad85c30.ago@gentoo> (raw)

commit:     53fcfbbc7e3c640717814bf93e2aaa283ad85c30
Author:     Agostino Sarubbo <ago <AT> gentoo <DOT> org>
AuthorDate: Fri Feb 26 12:07:08 2021 +0000
Commit:     Agostino Sarubbo <ago <AT> gentoo <DOT> org>
CommitDate: Fri Feb 26 12:07:08 2021 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=53fcfbbc

dev-python/cx_Freeze: amd64 stable wrt bug #772455

Package-Manager: Portage-3.0.13, Repoman-3.0.2
RepoMan-Options: --include-arches="amd64"
Signed-off-by: Agostino Sarubbo <ago <AT> gentoo.org>

 dev-python/cx_Freeze/cx_Freeze-6.5.3.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-python/cx_Freeze/cx_Freeze-6.5.3.ebuild b/dev-python/cx_Freeze/cx_Freeze-6.5.3.ebuild
index 5e32bd03118..69c9cd66a0d 100644
--- a/dev-python/cx_Freeze/cx_Freeze-6.5.3.ebuild
+++ b/dev-python/cx_Freeze/cx_Freeze-6.5.3.ebuild
@@ -13,7 +13,7 @@ SRC_URI="mirror://pypi/${PN:0:1}/${PN}/${P}.tar.gz"
 
 LICENSE="PYTHON"
 SLOT="0"
-KEYWORDS="~amd64 x86"
+KEYWORDS="amd64 x86"
 
 PATCHES=(
 	# bug #491602


             reply	other threads:[~2021-02-26 12:07 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-26 12:07 Agostino Sarubbo [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-07-19 11:10 [gentoo-commits] repo/gentoo:master commit in: dev-python/cx_Freeze/ Michał Górny
2023-07-17  7:34 Michał Górny
2023-06-28 17:17 Michał Górny
2023-06-27  5:19 Jakov Smolić
2023-06-18 17:07 Michał Górny
2023-06-07  5:09 Michał Górny
2023-05-24  7:02 Michał Górny
2023-05-23 16:00 Arthur Zamarin
2023-04-09  6:08 Michał Górny
2023-04-03 19:14 Arthur Zamarin
2023-04-03 19:14 Arthur Zamarin
2023-02-28  8:01 Sergey Popov
2023-02-09 18:09 Sergey Popov
2023-02-09 18:06 Sergey Popov
2022-12-17  7:03 Michał Górny
2022-12-16 20:59 Arthur Zamarin
2022-12-10  9:15 Arthur Zamarin
2022-11-19 16:52 Michał Górny
2022-11-19 16:40 Sam James
2022-11-19  9:05 Sam James
2022-11-02  7:37 Michał Górny
2022-10-26 18:42 Arthur Zamarin
2022-10-13 18:15 Michał Górny
2022-07-10 18:54 Michał Górny
2022-07-10 16:58 Sam James
2022-07-10 16:56 Sam James
2022-06-22 17:02 Arthur Zamarin
2022-06-05  9:14 Michał Górny
2022-06-04 17:48 Michał Górny
2022-01-09  5:13 Michał Górny
2022-01-09  1:08 Sam James
2022-01-08 18:03 Jakov Smolić
2021-12-08  5:37 Michał Górny
2021-11-28  7:50 Arthur Zamarin
2021-11-27  7:09 Arthur Zamarin
2021-09-19  0:58 Sam James
2021-08-26  7:43 Sergey Popov
2021-05-19  0:19 Sam James
2021-05-19  0:19 Sam James
2021-04-15  9:13 Sergey Popov
2021-01-24 19:50 Michał Górny
2021-01-13 20:16 Michał Górny
2021-01-13 19:05 Sam James
2021-01-13 19:04 Sam James
2020-10-16  7:29 Sergey Popov
2020-10-16  7:29 Sergey Popov
2020-05-11 16:48 Michał Górny
2020-05-11  9:44 Agostino Sarubbo
2020-03-10 19:20 Sergey Popov
2018-06-25  9:53 Jason Zaman
2018-03-18 19:19 Michał Górny
2017-07-14 12:53 Sergey Popov
2016-02-26 18:37 Sergey Popov

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=1614341228.53fcfbbc7e3c640717814bf93e2aaa283ad85c30.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