From: "Sergei Trofimovich" <slyfox@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/olefile/
Date: Sat, 25 Aug 2018 18:15:04 +0000 (UTC) [thread overview]
Message-ID: <1535220898.86727c8d546ba0395f965b0d004e3ac8514c2720.slyfox@gentoo> (raw)
commit: 86727c8d546ba0395f965b0d004e3ac8514c2720
Author: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
AuthorDate: Sat Aug 25 18:13:48 2018 +0000
Commit: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
CommitDate: Sat Aug 25 18:14:58 2018 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=86727c8d
dev-python/olefile: keyworded 0.45.1 for ppc, bug #659320
Package-Manager: Portage-2.3.48, Repoman-2.3.10
RepoMan-Options: --include-arches="ppc"
dev-python/olefile/olefile-0.45.1.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-python/olefile/olefile-0.45.1.ebuild b/dev-python/olefile/olefile-0.45.1.ebuild
index f26085310c9..7611f446918 100644
--- a/dev-python/olefile/olefile-0.45.1.ebuild
+++ b/dev-python/olefile/olefile-0.45.1.ebuild
@@ -13,7 +13,7 @@ SRC_URI="https://github.com/decalage2/${PN}/archive/v${PV}.tar.gz -> ${P}.tar.gz
LICENSE="BSD-2"
SLOT="0"
-KEYWORDS="~amd64 ~arm64 ~ppc64 ~x86 ~amd64-linux ~x86-linux"
+KEYWORDS="~amd64 ~arm64 ~ppc ~ppc64 ~x86 ~amd64-linux ~x86-linux"
IUSE="doc"
RDEPEND=""
next reply other threads:[~2018-08-25 18:15 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-25 18:15 Sergei Trofimovich [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-09-07 6:13 [gentoo-commits] repo/gentoo:master commit in: dev-python/olefile/ Arthur Zamarin
2024-05-11 11:05 Michał Górny
2023-12-20 15:51 Michał Górny
2023-12-20 15:49 Michał Górny
2023-12-04 18:39 Michał Górny
2023-05-25 16:27 Michał Górny
2023-05-25 16:27 Michał Górny
2022-06-12 14:25 Michał Górny
2022-06-12 12:46 Sam James
2022-05-11 6:19 Michał Górny
2022-05-11 6:19 Michał Górny
2022-04-26 3:32 Sam James
2022-01-06 22:59 James Le Cuirot
2021-09-23 20:13 Sam James
2021-08-28 8:16 Arthur Zamarin
2021-08-28 8:16 Arthur Zamarin
2021-06-22 17:01 Marek Szuba
2021-05-07 11:58 Michał Górny
2021-02-14 3:08 Sam James
2020-11-19 19:52 Michał Górny
2020-09-28 15:53 Michał Górny
2020-08-09 16:56 Sergei Trofimovich
2020-06-05 13:13 Michał Górny
2020-03-28 11:21 Michał Górny
2019-12-17 7:27 Sergei Trofimovich
2019-11-25 12:35 Michał Górny
2019-11-24 19:31 Michał Górny
2019-06-05 7:12 Agostino Sarubbo
2019-06-04 13:17 Agostino Sarubbo
2019-05-02 21:24 Mikle Kolyada
2019-04-16 23:29 Aaron Bauman
2019-04-01 19:58 Thomas Deutschmann
2019-03-20 11:23 Mikle Kolyada
2019-03-16 21:39 Agostino Sarubbo
2019-03-10 22:20 Jeroen Roovers
2019-01-02 3:30 Matt Turner
2018-12-29 12:05 Sergei Trofimovich
2018-12-29 12:05 Sergei Trofimovich
2018-12-09 9:58 Mikle Kolyada
2018-10-07 22:04 Matt Turner
2018-10-07 22:04 Matt Turner
2018-10-05 4:10 Thomas Deutschmann
2018-10-01 13:07 Virgil Dupras
2018-09-16 19:07 Virgil Dupras
2018-09-07 18:46 Virgil Dupras
2018-08-25 18:15 Sergei Trofimovich
2018-08-08 21:14 Mikle Kolyada
2018-08-05 11:33 Sergei Trofimovich
2018-08-05 11:33 Sergei Trofimovich
2018-07-26 21:00 Virgil Dupras
2018-07-26 20:00 Virgil Dupras
2018-07-16 1:22 Mikle Kolyada
2018-03-31 19:25 Mart Raudsepp
2017-07-11 20:33 Sebastien Fabbro
2017-07-11 20:33 Sebastien Fabbro
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=1535220898.86727c8d546ba0395f965b0d004e3ac8514c2720.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