From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/osc-lib/
Date: Wed, 29 Jun 2022 00:11:06 +0000 (UTC) [thread overview]
Message-ID: <1656461430.1648f438404af91cc849863a58948df0fc54f312.sam@gentoo> (raw)
commit: 1648f438404af91cc849863a58948df0fc54f312
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Wed Jun 29 00:10:30 2022 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Wed Jun 29 00:10:30 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=1648f438
dev-python/osc-lib: Stabilize 2.6.0 ALLARCHES, #854942
Signed-off-by: Sam James <sam <AT> gentoo.org>
dev-python/osc-lib/osc-lib-2.6.0.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-python/osc-lib/osc-lib-2.6.0.ebuild b/dev-python/osc-lib/osc-lib-2.6.0.ebuild
index 7971a2fec01b..4b1581252d95 100644
--- a/dev-python/osc-lib/osc-lib-2.6.0.ebuild
+++ b/dev-python/osc-lib/osc-lib-2.6.0.ebuild
@@ -14,7 +14,7 @@ SRC_URI="mirror://pypi/${PN:0:1}/${PN}/${P}.tar.gz"
LICENSE="Apache-2.0"
SLOT="0"
-KEYWORDS="~amd64 ~arm ~arm64 ~riscv ~x86 ~amd64-linux ~x86-linux"
+KEYWORDS="amd64 ~arm ~arm64 ~riscv x86 ~amd64-linux ~x86-linux"
RDEPEND="
>=dev-python/cliff-3.2.0[${PYTHON_USEDEP}]
next reply other threads:[~2022-06-29 0:11 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-29 0:11 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-12-07 12:03 [gentoo-commits] repo/gentoo:master commit in: dev-python/osc-lib/ Sam James
2024-11-21 6:01 Michał Górny
2024-07-27 9:53 Michał Górny
2024-07-27 7:41 Arthur Zamarin
2024-07-07 14:36 Michał Górny
2024-07-04 12:37 Michał Górny
2024-03-09 11:30 Michał Górny
2024-03-09 11:03 Jakov Smolić
2024-02-23 3:40 Michał Górny
2024-01-29 10:11 Michał Górny
2024-01-29 8:01 Sam James
2024-01-13 8:20 Michał Górny
2023-11-29 10:35 Michał Górny
2023-11-29 10:33 Michał Górny
2023-11-24 15:22 Arthur Zamarin
2023-11-14 20:06 Michał Górny
2023-11-08 12:53 Michał Górny
2023-09-25 18:52 Michał Górny
2023-09-25 17:33 Arthur Zamarin
2023-08-25 9:49 Michał Górny
2023-06-11 16:18 Michał Górny
2023-06-11 15:04 Sam James
2023-05-10 3:13 Michał Górny
2023-03-17 17:19 Michał Górny
2023-03-17 16:57 Sam James
2023-02-14 4:57 Michał Górny
2022-11-14 6:52 Arthur Zamarin
2022-09-26 6:06 Michał Górny
2022-08-24 19:36 Arthur Zamarin
2022-08-18 9:48 Michał Górny
2022-08-18 7:01 Agostino Sarubbo
2022-07-16 8:02 Michał Górny
2022-06-29 3:56 Michał Górny
2022-06-05 5:36 Michał Górny
2022-05-28 21:12 Jakov Smolić
2022-05-21 6:47 Michał Górny
2022-04-01 18:45 Michał Górny
2022-04-01 17:46 Arthur Zamarin
2022-04-01 17:45 Arthur Zamarin
2022-02-24 18:08 Michał Górny
2022-02-19 0:05 Michał Górny
2021-10-31 20:26 Michał Górny
2021-09-30 12:18 Arthur Zamarin
2021-01-24 0:07 Sam James
2020-11-18 9:43 Michał Górny
2020-11-18 9:43 Michał Górny
2020-11-17 21:15 Thomas Deutschmann
2020-11-14 22:00 Michał Górny
2020-10-11 1:29 Matthew Thode
2020-07-18 22:30 Matthew Thode
2020-06-20 19:23 Matthew Thode
2019-05-11 19:25 Matthew Thode
2019-04-10 22:44 Matthew Thode
2018-09-28 20:33 Matt Thode
2018-09-05 21:33 Matt Thode
2018-06-24 14:22 Pacho Ramos
2018-03-31 1:54 Matt Thode
2018-02-24 5:51 Matt Thode
2017-08-28 21:52 Matt Thode
2017-02-27 5:45 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=1656461430.1648f438404af91cc849863a58948df0fc54f312.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