From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/flask-sqlalchemy/
Date: Mon, 17 Oct 2022 19:47:29 +0000 (UTC) [thread overview]
Message-ID: <1666036027.a9d23da5b8d2aacb1f7cacc0be0c80d6070eb648.sam@gentoo> (raw)
commit: a9d23da5b8d2aacb1f7cacc0be0c80d6070eb648
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Mon Oct 17 19:46:49 2022 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Mon Oct 17 19:47:07 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a9d23da5
dev-python/flask-sqlalchemy: Keyword 3.0.2 arm, #875188
Signed-off-by: Sam James <sam <AT> gentoo.org>
dev-python/flask-sqlalchemy/flask-sqlalchemy-3.0.2.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-python/flask-sqlalchemy/flask-sqlalchemy-3.0.2.ebuild b/dev-python/flask-sqlalchemy/flask-sqlalchemy-3.0.2.ebuild
index 4f1c66408c0b..bba4a508aee3 100644
--- a/dev-python/flask-sqlalchemy/flask-sqlalchemy-3.0.2.ebuild
+++ b/dev-python/flask-sqlalchemy/flask-sqlalchemy-3.0.2.ebuild
@@ -21,7 +21,7 @@ S="${WORKDIR}/${MY_P}"
LICENSE="BSD"
SLOT="0"
-KEYWORDS="~amd64 ~arm64 ~ppc64 ~riscv ~x86"
+KEYWORDS="~amd64 ~arm ~arm64 ~ppc64 ~riscv ~x86"
RDEPEND="
>=dev-python/flask-2.2[${PYTHON_USEDEP}]
next reply other threads:[~2022-10-17 19:47 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-17 19:47 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-06-18 19:10 [gentoo-commits] repo/gentoo:master commit in: dev-python/flask-sqlalchemy/ Michał Górny
2023-11-24 14:34 Michał Górny
2023-10-14 18:40 Michał Górny
2023-10-14 16:52 Arthur Zamarin
2023-09-12 5:50 Michał Górny
2023-07-24 12:40 Michał Górny
2023-07-24 12:32 Jakov Smolić
2023-06-22 5:08 Michał Górny
2023-06-20 5:38 Michał Górny
2023-06-07 9:27 Sam James
2023-05-20 7:15 Michał Górny
2023-05-20 7:15 Michał Górny
2023-03-03 19:16 Michał Górny
2023-03-03 19:16 Michał Górny
2023-03-03 19:16 Michał Górny
2023-03-03 18:50 Arthur Zamarin
2023-01-31 19:09 Arthur Zamarin
2022-11-19 9:06 Arthur Zamarin
2022-11-19 9:05 Sam James
2022-11-06 3:59 Sam James
2022-10-14 16:22 Arthur Zamarin
2022-10-12 11:18 Michał Górny
2022-10-07 7:03 Michał Górny
2022-10-05 5:53 Arthur Zamarin
2022-10-05 5:20 Arthur Zamarin
2022-05-18 16:15 Andrew Ammerlaan
2022-05-18 14:22 Andrew Ammerlaan
2022-01-28 18:41 Arthur Zamarin
2021-08-01 21:12 Michał Górny
2021-04-22 15:07 Michał Górny
2021-04-22 15:07 Michał Górny
2021-04-22 12:08 Sam James
2021-03-18 23:28 Michał Górny
2021-03-18 23:28 Michał Górny
2020-08-18 5:28 Sam James
2020-07-30 20:41 Michał Górny
2020-07-30 20:03 Sam James
2020-07-30 19:39 Sam James
2020-07-15 5:04 Michał Górny
2020-06-12 15:40 Michał Górny
2020-06-12 15:40 Michał Górny
2020-03-27 9:16 Michał Górny
2020-03-27 9:16 Michał Górny
2020-03-27 9:16 Michał Górny
2020-03-17 19:52 Michał Górny
2019-12-28 19:38 Louis Sautier
2019-12-28 19:38 Louis Sautier
2019-12-03 21:36 Aaron Bauman
2019-12-03 3:02 Aaron Bauman
2019-10-18 0:24 Aaron W. Swenson
2018-07-09 18:58 Mikle Kolyada
2018-07-09 1:29 Thomas Deutschmann
2017-01-18 11:57 Agostino Sarubbo
2017-01-17 16:22 Agostino Sarubbo
2016-04-17 11:39 Ian Delaney
2016-02-14 18:56 Patrick Lauer
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=1666036027.a9d23da5b8d2aacb1f7cacc0be0c80d6070eb648.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