From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/ytmusicapi/
Date: Wed, 29 Nov 2023 11:04:21 +0000 (UTC) [thread overview]
Message-ID: <1701255854.2bbfe42f409656741d2b409fb51757a0776e2c7a.mgorny@gentoo> (raw)
commit: 2bbfe42f409656741d2b409fb51757a0776e2c7a
Author: Michał Górny <mgorny <AT> gentoo <DOT> org>
AuthorDate: Wed Nov 29 11:03:31 2023 +0000
Commit: Michał Górny <mgorny <AT> gentoo <DOT> org>
CommitDate: Wed Nov 29 11:04:14 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=2bbfe42f
dev-python/ytmusicapi: Stabilize 1.3.2 ALLARCHES, #918846
Signed-off-by: Michał Górny <mgorny <AT> gentoo.org>
dev-python/ytmusicapi/ytmusicapi-1.3.2.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-python/ytmusicapi/ytmusicapi-1.3.2.ebuild b/dev-python/ytmusicapi/ytmusicapi-1.3.2.ebuild
index 75a0cdb04926..25bb762afaca 100644
--- a/dev-python/ytmusicapi/ytmusicapi-1.3.2.ebuild
+++ b/dev-python/ytmusicapi/ytmusicapi-1.3.2.ebuild
@@ -13,7 +13,7 @@ HOMEPAGE="https://ytmusicapi.readthedocs.io/
https://github.com/sigma67/ytmusicapi/"
LICENSE="MIT"
-KEYWORDS="~amd64 ~x86"
+KEYWORDS="amd64 ~x86"
SLOT="0"
RDEPEND="dev-python/requests[${PYTHON_USEDEP}]"
next reply other threads:[~2023-11-29 11:04 UTC|newest]
Thread overview: 83+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-29 11:04 Michał Górny [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-09-14 12:39 [gentoo-commits] repo/gentoo:master commit in: dev-python/ytmusicapi/ Michał Górny
2024-09-14 12:28 Arthur Zamarin
2024-08-24 23:48 Maciej Barć
2024-08-10 7:31 Michał Górny
2024-08-10 7:25 Michał Górny
2024-08-03 18:58 Michał Górny
2024-08-03 16:48 Jakov Smolić
2024-07-25 16:48 Maciej Barć
2024-07-20 13:27 Michał Górny
2024-07-20 11:14 Arthur Zamarin
2024-07-15 7:10 Maciej Barć
2024-07-04 12:44 Maciej Barć
2024-06-12 13:10 Michał Górny
2024-06-12 11:10 Arthur Zamarin
2024-06-07 17:29 Michał Górny
2024-06-07 16:56 Arthur Zamarin
2024-05-27 21:03 Maciej Barć
2024-05-21 0:51 Maciej Barć
2024-05-11 18:21 Maciej Barć
2024-05-06 8:47 Arthur Zamarin
2024-03-23 11:58 Michał Górny
2024-03-23 11:53 Michał Górny
2024-03-22 12:37 Michał Górny
2024-03-22 6:14 Arthur Zamarin
2024-03-08 22:18 Maciej Barć
2024-03-02 16:32 Maciej Barć
2024-02-23 1:05 Maciej Barć
2024-02-20 14:13 Michał Górny
2024-02-20 14:06 Jakov Smolić
2024-02-05 11:28 Maciej Barć
2024-01-30 19:58 Maciej Barć
2024-01-25 4:43 Michał Górny
2024-01-25 0:44 Sam James
2024-01-21 20:47 Maciej Barć
2024-01-06 18:42 Maciej Barć
2024-01-06 18:42 Maciej Barć
2024-01-05 3:02 Maciej Barć
2024-01-05 3:02 Maciej Barć
2024-01-01 20:29 Maciej Barć
2023-11-29 11:15 Michał Górny
2023-11-26 4:14 Michał Górny
2023-11-25 23:09 Sam James
2023-10-26 13:13 Maciej Barć
2023-10-26 13:13 Maciej Barć
2023-10-04 8:11 Maciej Barć
2023-10-02 4:22 Michał Górny
2023-10-01 18:07 Arthur Zamarin
2023-09-21 5:09 Sam James
2023-08-31 14:41 Maciej Barć
2023-08-20 20:32 Maciej Barć
2023-08-04 2:42 Michał Górny
2023-08-03 20:45 Sam James
2023-07-17 17:56 Michał Górny
2023-07-17 16:53 Arthur Zamarin
2023-07-03 22:42 Maciej Barć
2023-06-16 21:02 Maciej Barć
2023-05-25 14:38 Michał Górny
2023-05-25 8:28 Arthur Zamarin
2023-05-05 13:43 Michał Górny
2023-05-05 7:31 Arthur Zamarin
2023-04-24 17:39 Maciej Barć
2023-04-24 17:39 Maciej Barć
2023-04-24 17:39 Maciej Barć
2023-04-20 0:03 Maciej Barć
2023-04-08 19:57 Maciej Barć
2023-04-08 19:57 Maciej Barć
2023-04-03 0:24 Maciej Barć
2023-03-27 17:16 Arthur Zamarin
2023-03-27 17:16 Arthur Zamarin
2023-03-16 4:13 Michał Górny
2023-01-21 9:13 Arthur Zamarin
2023-01-16 6:11 Michał Górny
2023-01-16 1:57 Maciej Barć
2023-01-15 23:05 Maciej Barć
2022-11-30 19:42 Arthur Zamarin
2022-11-14 5:07 Michał Górny
2022-10-05 2:36 Maciej Barć
2022-09-26 22:51 Maciej Barć
2022-05-16 13:30 Michał Górny
2022-05-10 20:37 Maciej Barć
2022-04-10 20:21 Maciej Barć
2022-04-04 15:47 Maciej Barć
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=1701255854.2bbfe42f409656741d2b409fb51757a0776e2c7a.mgorny@gentoo \
--to=mgorny@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