From: "Agostino Sarubbo" <ago@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/hcloud-python/
Date: Sat, 22 Aug 2020 11:37:34 +0000 (UTC) [thread overview]
Message-ID: <1598096242.defbf5b8a60448d6db498071e9253b9848e96194.ago@gentoo> (raw)
commit: defbf5b8a60448d6db498071e9253b9848e96194
Author: Agostino Sarubbo <ago <AT> gentoo <DOT> org>
AuthorDate: Sat Aug 22 11:37:22 2020 +0000
Commit: Agostino Sarubbo <ago <AT> gentoo <DOT> org>
CommitDate: Sat Aug 22 11:37:22 2020 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=defbf5b8
dev-python/hcloud-python: amd64 stable wrt bug #738528
Closes: https://bugs.gentoo.org/738528
Package-Manager: Portage-2.3.103, Repoman-2.3.23
Signed-off-by: Agostino Sarubbo <ago <AT> gentoo.org>
dev-python/hcloud-python/hcloud-python-1.8.2.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-python/hcloud-python/hcloud-python-1.8.2.ebuild b/dev-python/hcloud-python/hcloud-python-1.8.2.ebuild
index 38732655eab..90f5fbfd78b 100644
--- a/dev-python/hcloud-python/hcloud-python-1.8.2.ebuild
+++ b/dev-python/hcloud-python/hcloud-python-1.8.2.ebuild
@@ -13,7 +13,7 @@ SRC_URI="https://github.com/hetznercloud/${PN}/archive/v${PV}.tar.gz -> ${P}.tar
LICENSE="MIT"
SLOT="0"
-KEYWORDS="~amd64"
+KEYWORDS="amd64"
IUSE="doc examples"
COMMON_DEPEND=">=dev-python/python-dateutil-2.7.5[${PYTHON_USEDEP}]
next reply other threads:[~2020-08-22 11:37 UTC|newest]
Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-22 11:37 Agostino Sarubbo [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-07-23 14:15 [gentoo-commits] repo/gentoo:master commit in: dev-python/hcloud-python/ Michał Górny
2023-07-23 13:43 Sam James
2023-07-23 6:53 Michał Górny
2023-07-15 3:04 Michał Górny
2023-07-04 2:59 Michał Górny
2023-07-01 5:22 Michał Górny
2023-06-30 13:06 Michał Górny
2023-06-30 2:56 Michał Górny
2023-06-23 6:06 Michał Górny
2023-06-20 5:48 Michał Górny
2023-06-20 5:38 Michał Górny
2023-06-18 17:21 Michał Górny
2023-06-18 16:23 Sam James
2023-05-13 16:04 Michał Górny
2023-05-13 10:42 Arthur Zamarin
2023-05-13 4:46 Michał Górny
2023-04-13 6:04 Michał Górny
2023-02-01 13:53 Agostino Sarubbo
2023-02-01 13:53 Agostino Sarubbo
2022-12-28 8:17 Michał Górny
2022-11-25 20:33 Arthur Zamarin
2022-11-25 19:11 Sam James
2022-10-25 20:30 Arthur Zamarin
2022-09-20 5:37 Michał Górny
2022-09-20 0:07 Sam James
2022-08-17 18:28 Arthur Zamarin
2022-08-17 18:28 Arthur Zamarin
2022-08-02 14:59 Agostino Sarubbo
2022-08-02 14:59 Agostino Sarubbo
2022-06-29 17:08 Arthur Zamarin
2021-09-18 19:43 Michał Górny
2021-09-18 17:18 Sam James
2021-08-26 8:24 Michał Górny
2021-08-26 8:24 Michał Górny
2021-08-26 4:41 Agostino Sarubbo
2021-08-18 6:56 Michał Górny
2021-08-17 7:28 Michał Górny
2021-08-11 7:06 Michał Górny
2021-07-17 7:03 Michał Górny
2021-05-05 7:21 Agostino Sarubbo
2021-05-05 7:20 Agostino Sarubbo
2021-04-06 21:26 Michał Górny
2021-04-06 21:26 Michał Górny
2020-12-17 17:09 Michał Górny
2020-11-10 7:44 Agostino Sarubbo
2020-09-16 6:54 Agostino Sarubbo
2020-09-16 6:54 Agostino Sarubbo
2020-08-11 13:54 Agostino Sarubbo
2020-08-11 11:05 Agostino Sarubbo
2020-07-22 13:14 Agostino Sarubbo
2020-07-20 15:15 Agostino Sarubbo
2020-07-20 15:15 Agostino Sarubbo
2020-07-10 15:14 Agostino Sarubbo
2020-06-09 13:39 Agostino Sarubbo
2020-05-18 15:19 Agostino Sarubbo
2020-05-06 7:22 Agostino Sarubbo
2020-03-04 10:29 Agostino Sarubbo
2020-02-21 12:52 Agostino Sarubbo
2020-01-11 14:01 Agostino Sarubbo
2020-01-11 13:56 Agostino Sarubbo
2019-11-20 12:00 Agostino Sarubbo
2019-11-12 13:47 Agostino Sarubbo
2019-10-09 13:47 Agostino Sarubbo
2019-10-09 13:46 Agostino Sarubbo
2019-09-16 9:46 Agostino Sarubbo
2019-09-02 11:52 Agostino Sarubbo
2019-07-19 15:20 Agostino Sarubbo
2019-06-26 8:32 Agostino Sarubbo
2019-05-30 18:41 Agostino Sarubbo
2019-04-29 8:26 Agostino Sarubbo
2019-04-29 7:34 Agostino Sarubbo
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=1598096242.defbf5b8a60448d6db498071e9253b9848e96194.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