From: "Sergei Trofimovich" <slyfox@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sci-libs/libgeotiff/
Date: Tue, 2 Jul 2019 08:28:47 +0000 (UTC) [thread overview]
Message-ID: <1562055980.401a209e45e48e8402fbb6d6522fcbf27cfb58c1.slyfox@gentoo> (raw)
commit: 401a209e45e48e8402fbb6d6522fcbf27cfb58c1
Author: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
AuthorDate: Tue Jul 2 08:26:20 2019 +0000
Commit: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
CommitDate: Tue Jul 2 08:26:20 2019 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=401a209e
sci-libs/libgeotiff: stable 1.4.1-r1 for ppc64, bug #688806
Package-Manager: Portage-2.3.68, Repoman-2.3.16
RepoMan-Options: --include-arches="ppc64"
Signed-off-by: Sergei Trofimovich <slyfox <AT> gentoo.org>
sci-libs/libgeotiff/libgeotiff-1.4.1-r1.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/sci-libs/libgeotiff/libgeotiff-1.4.1-r1.ebuild b/sci-libs/libgeotiff/libgeotiff-1.4.1-r1.ebuild
index 27e8b6cd330..87d53b8e09f 100644
--- a/sci-libs/libgeotiff/libgeotiff-1.4.1-r1.ebuild
+++ b/sci-libs/libgeotiff/libgeotiff-1.4.1-r1.ebuild
@@ -13,7 +13,7 @@ SRC_URI="http://download.osgeo.org/geotiff/${PN}/${MY_P}.tar.gz"
LICENSE="GPL-2"
SLOT="0"
-KEYWORDS="amd64 ~arm ~arm64 ~ia64 ppc ~ppc64 x86 ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~x86-macos"
+KEYWORDS="amd64 ~arm ~arm64 ~ia64 ppc ppc64 x86 ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~x86-macos"
IUSE="debug doc static-libs"
RDEPEND="
next reply other threads:[~2019-07-02 8:28 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-02 8:28 Sergei Trofimovich [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-02-20 23:24 [gentoo-commits] repo/gentoo:master commit in: sci-libs/libgeotiff/ Sam James
2025-02-20 1:12 Sam James
2025-02-20 1:12 Sam James
2025-02-20 1:12 Sam James
2022-12-18 8:03 Sam James
2022-12-16 1:40 Sam James
2022-12-04 9:23 WANG Xuerui
2022-12-02 18:12 Arthur Zamarin
2022-11-25 9:35 Arthur Zamarin
2022-11-25 9:26 Sam James
2022-11-25 9:03 Arthur Zamarin
2022-11-25 8:22 Arthur Zamarin
2022-11-25 8:09 Sam James
2021-09-17 14:15 Agostino Sarubbo
2021-09-16 18:56 Sam James
2021-09-16 8:03 Agostino Sarubbo
2021-09-15 7:59 Agostino Sarubbo
2021-08-14 23:15 Marek Szuba
2021-07-06 4:12 Sam James
2021-05-27 21:06 David Seifert
2021-02-26 19:06 Sam James
2021-02-25 11:33 Sam James
2021-02-24 20:25 Sam James
2021-02-24 20:24 Sam James
2021-01-25 22:18 Sam James
2021-01-06 15:17 Fabian Groffen
2020-04-10 9:31 Andreas Sturmlechner
2020-04-10 8:05 Mart Raudsepp
2020-02-12 10:47 Agostino Sarubbo
2020-02-12 7:57 Agostino Sarubbo
2020-02-12 7:53 Agostino Sarubbo
2020-02-12 0:23 Piotr Karbowski
2019-12-29 0:20 Andreas Sturmlechner
2019-07-23 14:51 Andreas Sturmlechner
2019-07-23 14:46 Aaron Bauman
2019-07-02 8:24 Sergei Trofimovich
2019-06-28 15:21 Agostino Sarubbo
2019-06-28 11:37 Agostino Sarubbo
2019-05-24 19:26 Andreas Sturmlechner
2019-05-24 19:26 Andreas Sturmlechner
2019-05-16 19:30 Aaron Bauman
2019-05-06 16:20 Andrey Grozin
2018-08-03 13:32 Amy Liffey
2018-03-28 4:16 Matt Turner
2017-12-19 22:30 Sergei Trofimovich
2017-07-20 20:57 Sergei Trofimovich
2017-07-11 8:41 Alexis Ballier
2016-02-27 12:54 Amy Winston
2016-02-27 12:54 Amy Winston
2016-02-27 12:54 Amy Winston
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=1562055980.401a209e45e48e8402fbb6d6522fcbf27cfb58c1.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