From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sci-libs/libgeotiff/
Date: Thu, 01 May 2025 17:58:31 +0000 (UTC) [thread overview]
Message-ID: <1746122272.7226a12ceebe35d46944b0c0f90584ea55cb0a48.sam@gentoo> (raw)
commit: 7226a12ceebe35d46944b0c0f90584ea55cb0a48
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Thu May 1 17:57:52 2025 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Thu May 1 17:57:52 2025 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=7226a12c
sci-libs/libgeotiff: Stabilize 1.7.4 amd64, #953813
Signed-off-by: Sam James <sam <AT> gentoo.org>
sci-libs/libgeotiff/libgeotiff-1.7.4.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/sci-libs/libgeotiff/libgeotiff-1.7.4.ebuild b/sci-libs/libgeotiff/libgeotiff-1.7.4.ebuild
index b3c63b312ce8..9a3646dca0d5 100644
--- a/sci-libs/libgeotiff/libgeotiff-1.7.4.ebuild
+++ b/sci-libs/libgeotiff/libgeotiff-1.7.4.ebuild
@@ -16,7 +16,7 @@ SRC_URI="https://download.osgeo.org/geotiff/${PN}/${P}.tar.gz"
LICENSE="GPL-2"
SLOT="0/5"
-KEYWORDS="~amd64 ~arm arm64 ~loong ~ppc ppc64 ~riscv x86 ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos"
+KEYWORDS="amd64 ~arm arm64 ~loong ~ppc ppc64 ~riscv x86 ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos"
# TODO: add tiff when resolved: https://github.com/OSGeo/libgeotiff/issues/125
IUSE="jpeg zlib"
next reply other threads:[~2025-05-01 17:58 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-01 17:58 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-05-01 17:34 [gentoo-commits] repo/gentoo:master commit in: sci-libs/libgeotiff/ Sam James
2025-05-01 17:34 Sam James
2025-05-01 17:34 Sam James
2025-02-20 23:24 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:28 Sergei Trofimovich
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=1746122272.7226a12ceebe35d46944b0c0f90584ea55cb0a48.sam@gentoo \
--to=sam@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