From: "Sergei Trofimovich" <slyfox@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/webencodings/
Date: Sat, 30 Jun 2018 17:55:06 +0000 (UTC) [thread overview]
Message-ID: <1530381294.ea9e9aee2cf4cd8c5941b35739f7e74e326f13e4.slyfox@gentoo> (raw)
commit: ea9e9aee2cf4cd8c5941b35739f7e74e326f13e4
Author: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
AuthorDate: Sat Jun 30 17:54:20 2018 +0000
Commit: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
CommitDate: Sat Jun 30 17:54:54 2018 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ea9e9aee
dev-python/webencodings: stable 0.5.1 for ia64, bug #659658
Bug: https://bugs.gentoo.org/659658
Package-Manager: Portage-2.3.41, Repoman-2.3.9
RepoMan-Options: --include-arches="ia64"
dev-python/webencodings/webencodings-0.5.1.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-python/webencodings/webencodings-0.5.1.ebuild b/dev-python/webencodings/webencodings-0.5.1.ebuild
index 1675fb1faac..38625e9e3ce 100644
--- a/dev-python/webencodings/webencodings-0.5.1.ebuild
+++ b/dev-python/webencodings/webencodings-0.5.1.ebuild
@@ -13,7 +13,7 @@ SRC_URI="mirror://pypi/${P:0:1}/${PN}/${P}.tar.gz"
LICENSE="BSD"
SLOT="0"
-KEYWORDS="~alpha amd64 ~arm arm64 ~hppa ~ia64 ~mips ~ppc ~ppc64 ~sparc x86 ~amd64-fbsd ~amd64-linux ~x86-linux ~x64-macos"
+KEYWORDS="~alpha amd64 ~arm arm64 ~hppa ia64 ~mips ~ppc ~ppc64 ~sparc x86 ~amd64-fbsd ~amd64-linux ~x86-linux ~x64-macos"
IUSE="test"
RDEPEND=""
next reply other threads:[~2018-06-30 17:55 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-30 17:55 Sergei Trofimovich [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-05-09 19:13 [gentoo-commits] repo/gentoo:master commit in: dev-python/webencodings/ Michał Górny
2023-05-24 8:36 Sam James
2023-03-16 4:13 Michał Górny
2022-06-13 8:23 Michał Górny
2022-06-13 7:07 Agostino Sarubbo
2022-05-11 17:54 Michał Górny
2022-05-11 17:54 Michał Górny
2021-09-25 21:27 James Le Cuirot
2021-05-07 11:58 Michał Górny
2020-07-27 10:02 Michał Górny
2020-05-26 16:23 Michał Górny
2020-05-26 16:23 Michał Górny
2020-03-29 11:51 Michał Górny
2020-03-29 11:51 Michał Górny
2020-03-29 11:51 Michał Górny
2020-03-25 15:27 Agostino Sarubbo
2020-03-25 14:52 Agostino Sarubbo
2020-03-25 13:27 Agostino Sarubbo
2020-03-25 13:12 Agostino Sarubbo
2020-03-25 12:36 Agostino Sarubbo
2020-03-25 12:23 Agostino Sarubbo
2019-11-27 1:13 Patrick McLean
2019-11-02 8:19 Mikle Kolyada
2019-01-05 17:19 Mikle Kolyada
2018-07-22 2:14 Mikle Kolyada
2018-07-20 15:53 Tobias Klausmann
2018-07-15 10:25 Sergei Trofimovich
2018-07-14 20:10 Sergei Trofimovich
2018-07-02 21:24 Sergei Trofimovich
2018-05-17 13:52 Thomas Deutschmann
2018-05-16 8:35 Agostino Sarubbo
2018-02-21 18:03 Michał Górny
2018-02-21 18:03 Michał Górny
2018-01-06 13:39 Michał Górny
2017-12-20 21:53 Sergei Trofimovich
2017-11-23 22:31 Matt Turner
2017-09-22 19:40 Sergei Trofimovich
2017-07-01 11:19 Sergei Trofimovich
2017-05-26 20:56 Mart Raudsepp
2017-05-26 18:36 Markus Meier
2017-05-23 20:00 Michael Weber
2017-05-18 20:00 Michael Weber
2017-05-17 19:22 Markus Meier
2017-05-10 20:10 Jeroen Roovers
2017-05-04 17:13 Zac Medico
2016-06-29 10:46 Patrick Lauer
2016-01-15 10:44 Justin Lecher
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=1530381294.ea9e9aee2cf4cd8c5941b35739f7e74e326f13e4.slyfox@gentoo \
--to=slyfox@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