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/bandit/
Date: Tue,  1 Jun 2021 06:59:34 +0000 (UTC)	[thread overview]
Message-ID: <1622530769.bf80e98145ba70258c4d4030938ae01124fc5a98.ago@gentoo> (raw)

commit:     bf80e98145ba70258c4d4030938ae01124fc5a98
Author:     Agostino Sarubbo <ago <AT> gentoo <DOT> org>
AuthorDate: Tue Jun  1 06:58:36 2021 +0000
Commit:     Agostino Sarubbo <ago <AT> gentoo <DOT> org>
CommitDate: Tue Jun  1 06:59:29 2021 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=bf80e981

dev-python/bandit: x86 stable wrt bug #793320

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

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

diff --git a/dev-python/bandit/bandit-1.7.0.ebuild b/dev-python/bandit/bandit-1.7.0.ebuild
index 03c2fb97c5d..2bd9f1e7505 100644
--- a/dev-python/bandit/bandit-1.7.0.ebuild
+++ b/dev-python/bandit/bandit-1.7.0.ebuild
@@ -13,7 +13,7 @@ SRC_URI="mirror://pypi/${PN:0:1}/${PN}/${P}.tar.gz"
 
 LICENSE="Apache-2.0"
 SLOT="0"
-KEYWORDS="amd64 ~arm ~arm64 ~s390 ~x86"
+KEYWORDS="amd64 ~arm ~arm64 ~s390 x86"
 IUSE="test"
 RESTRICT="!test? ( test )"
 


             reply	other threads:[~2021-06-01  6:59 UTC|newest]

Thread overview: 74+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-01  6:59 Agostino Sarubbo [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-09-24  6:41 [gentoo-commits] repo/gentoo:master commit in: dev-python/bandit/ Michał Górny
2024-06-29 16:58 Michał Górny
2024-06-29  8:25 Sam James
2024-06-13  4:05 Michał Górny
2024-05-22  8:03 Michał Górny
2024-03-23 10:45 Michał Górny
2024-03-23 10:41 Michał Górny
2024-03-09  7:18 Michał Górny
2024-02-08 15:37 Michał Górny
2024-02-08 15:28 Michał Górny
2024-01-24  7:01 Michał Górny
2023-12-24  5:59 Michał Górny
2023-12-09  6:53 Michał Górny
2023-11-08 11:57 Michał Górny
2023-04-11 18:39 Michał Górny
2023-04-11 18:32 Arthur Zamarin
2023-03-10  9:00 Sam James
2023-03-10  4:16 Michał Górny
2022-11-12 11:59 Arthur Zamarin
2022-05-28 21:12 Jakov Smolić
2022-04-25 17:17 Sam James
2022-03-31 12:42 Michał Górny
2022-03-31 12:33 Jakov Smolić
2022-03-09 20:06 Arthur Zamarin
2022-02-28  8:28 Michał Górny
2022-02-27 18:35 Michał Górny
2022-02-27  9:18 Michał Górny
2022-02-24 18:46 Michał Górny
2022-01-28 23:01 Michał Górny
2022-01-26  7:33 Michał Górny
2021-12-17  9:15 Michał Górny
2021-12-14  7:14 Michał Górny
2021-12-13 20:29 Jakov Smolić
2021-12-13 18:58 Arthur Zamarin
2021-12-13 18:50 Jakov Smolić
2021-11-12 19:50 Arthur Zamarin
2021-11-12 19:50 Arthur Zamarin
2021-10-17  7:33 Michał Górny
2021-06-01  6:32 Agostino Sarubbo
2021-04-29  1:51 William Hubbs
2020-11-18 10:28 Michał Górny
2020-11-18  6:53 Agostino Sarubbo
2020-11-14  0:09 Thomas Deutschmann
2020-10-28  5:38 Matthew Thode
2020-10-16  2:04 Matthew Thode
2020-02-24 16:52 Matthew Thode
2020-01-26 23:10 Matthew Thode
2020-01-26 21:46 Matthew Thode
2019-12-02 21:13 Aaron Bauman
2019-01-28  0:25 Matthew Thode
2019-01-28  0:25 Matthew Thode
2018-08-20  7:04 Mikle Kolyada
2018-02-13 15:57 Mart Raudsepp
2018-02-13 13:59 Mart Raudsepp
2017-03-13  1:30 Zac Medico
2017-02-09 12:10 Matt Thode
2017-01-12 18:02 Matt Thode
2016-12-03  4:17 Matt Thode
2016-11-16 15:38 Matt Thode
2016-04-05 22:39 Matt Thode
2016-04-05 14:48 Matt Thode
2016-01-28  5:30 Matt Thode
2016-01-27  4:23 Matt Thode
2015-12-17 18:40 Matt Thode
2015-11-10  8:24 Agostino Sarubbo
2015-11-10  8:19 Agostino Sarubbo
2015-10-14 22:47 Matt Thode
2015-10-12 22:32 Matt Thode
2015-10-12 16:33 Matt Thode
2015-10-08 21:45 Matt Thode
2015-08-25 23:47 Matt Thode
2015-08-14 20:20 Matt Thode
2015-08-12 22:47 Matt Thode

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=1622530769.bf80e98145ba70258c4d4030938ae01124fc5a98.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