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/ruamel-std-pathlib/
Date: Tue, 11 Feb 2020 19:43:25 +0000 (UTC)	[thread overview]
Message-ID: <1581450191.3c2db5541aecd7e27a973327cf547987b177e474.ago@gentoo> (raw)

commit:     3c2db5541aecd7e27a973327cf547987b177e474
Author:     Agostino Sarubbo <ago <AT> gentoo <DOT> org>
AuthorDate: Tue Feb 11 19:40:17 2020 +0000
Commit:     Agostino Sarubbo <ago <AT> gentoo <DOT> org>
CommitDate: Tue Feb 11 19:43:11 2020 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=3c2db554

dev-python/ruamel-std-pathlib: amd64 stable wrt bug #706146

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

 dev-python/ruamel-std-pathlib/ruamel-std-pathlib-0.6.4-r1.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-python/ruamel-std-pathlib/ruamel-std-pathlib-0.6.4-r1.ebuild b/dev-python/ruamel-std-pathlib/ruamel-std-pathlib-0.6.4-r1.ebuild
index 2a675524e68..1a4104bb030 100644
--- a/dev-python/ruamel-std-pathlib/ruamel-std-pathlib-0.6.4-r1.ebuild
+++ b/dev-python/ruamel-std-pathlib/ruamel-std-pathlib-0.6.4-r1.ebuild
@@ -15,7 +15,7 @@ SRC_URI="https://bitbucket.org/${MY_PN/.//}/get/${PV}.tar.gz -> ${P}.tar.gz"
 
 LICENSE="MIT"
 SLOT="0"
-KEYWORDS="~amd64 ~arm64 ~x86"
+KEYWORDS="amd64 ~arm64 ~x86"
 
 BDEPEND="dev-python/setuptools[${PYTHON_USEDEP}]"
 


             reply	other threads:[~2020-02-11 19:43 UTC|newest]

Thread overview: 63+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-11 19:43 Agostino Sarubbo [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-12-08 14:24 [gentoo-commits] repo/gentoo:master commit in: dev-python/ruamel-std-pathlib/ Arthur Zamarin
2023-11-30 21:43 James Le Cuirot
2023-09-01 19:26 Arthur Zamarin
2023-05-26 17:44 Michał Górny
2023-03-11 17:12 Michał Górny
2023-03-11 17:06 Sam James
2023-03-11 16:10 Arthur Zamarin
2023-03-11 16:07 Arthur Zamarin
2023-03-11 16:04 Arthur Zamarin
2023-03-11 16:00 Arthur Zamarin
2023-03-11 16:00 Sam James
2023-03-11 16:00 Sam James
2023-02-20 21:29 Arthur Zamarin
2023-02-07 16:54 Sam James
2023-02-07 16:54 Sam James
2023-02-07 14:18 Michał Górny
2022-05-23 22:43 Marek Szuba
2022-04-20 17:24 Michał Górny
2022-04-20 17:24 Michał Górny
2022-04-20 14:12 Jakov Smolić
2022-04-13 14:46 Sam James
2022-04-11 19:58 Michał Górny
2022-04-10  8:58 Michał Górny
2022-03-16  8:07 Michał Górny
2022-03-16  8:07 Michał Górny
2022-03-15 17:56 Jakov Smolić
2022-02-22 19:01 Michał Górny
2022-02-20 14:03 Michał Górny
2022-01-28 11:32 Arthur Zamarin
2021-11-19 11:44 Arthur Zamarin
2021-10-18  7:35 Michał Górny
2021-06-22 13:10 Marek Szuba
2021-05-13 19:11 Marek Szuba
2021-04-27 11:05 Marek Szuba
2021-04-27 11:05 Marek Szuba
2021-04-16  0:40 Sam James
2021-04-12 15:55 Sam James
2021-04-12 15:55 Sam James
2021-04-12 15:55 Sam James
2021-04-12 15:55 Sam James
2021-04-12 15:52 Sam James
2021-04-12 15:50 Sam James
2021-03-15 10:35 Marek Szuba
2021-03-15  6:38 Sam James
2021-03-12 19:27 Sergei Trofimovich
2021-03-12 19:27 Sergei Trofimovich
2021-03-12 19:27 Sergei Trofimovich
2021-03-12 19:27 Sergei Trofimovich
2021-03-12 19:27 Sergei Trofimovich
2021-03-12 16:14 Marek Szuba
2021-03-10 12:34 Marek Szuba
2020-09-02  7:41 Mikle Kolyada
2020-05-16  7:09 Joonas Niilola
2020-03-29  7:31 Michał Górny
2019-12-07  0:40 Patrick McLean
2019-06-24  8:29 Andrey Utkin
2019-06-24  8:29 Andrey Utkin
2019-06-24  8:29 Andrey Utkin
2019-01-31  9:17 Tim Harder
2018-06-08 22:35 Mart Raudsepp
2018-03-30 18:35 Aaron Bauman
2018-02-07 12:18 Andrey Utkin

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=1581450191.3c2db5541aecd7e27a973327cf547987b177e474.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