From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: media-libs/lensfun/
Date: Sat, 29 Apr 2023 20:25:31 +0000 (UTC) [thread overview]
Message-ID: <1682799916.78b3e02553027b32f1c461cb48ec3f6661ad1103.sam@gentoo> (raw)
commit: 78b3e02553027b32f1c461cb48ec3f6661ad1103
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sat Apr 29 20:25:16 2023 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sat Apr 29 20:25:16 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=78b3e025
media-libs/lensfun: Stabilize 0.3.4_rc1 ppc, #904653
Signed-off-by: Sam James <sam <AT> gentoo.org>
media-libs/lensfun/lensfun-0.3.4_rc1.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/media-libs/lensfun/lensfun-0.3.4_rc1.ebuild b/media-libs/lensfun/lensfun-0.3.4_rc1.ebuild
index 437048e528df..c03e1809014f 100644
--- a/media-libs/lensfun/lensfun-0.3.4_rc1.ebuild
+++ b/media-libs/lensfun/lensfun-0.3.4_rc1.ebuild
@@ -13,7 +13,7 @@ S="${WORKDIR}/${P/_rc/-RC}"
LICENSE="LGPL-3 CC-BY-SA-3.0" # See README for reasoning.
SLOT="0"
-KEYWORDS="~alpha amd64 ~arm arm64 ~hppa ~ia64 ~loong ~mips ~ppc ppc64 ~riscv ~s390 ~sparc x86 ~amd64-linux ~x86-linux"
+KEYWORDS="~alpha amd64 ~arm arm64 ~hppa ~ia64 ~loong ~mips ppc ppc64 ~riscv ~s390 ~sparc x86 ~amd64-linux ~x86-linux"
IUSE="doc cpu_flags_x86_sse cpu_flags_x86_sse2 test"
REQUIRED_USE="${PYTHON_REQUIRED_USE}"
next reply other threads:[~2023-04-29 20:25 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-29 20:25 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-06-10 23:46 [gentoo-commits] repo/gentoo:master commit in: media-libs/lensfun/ Sam James
2024-05-28 13:19 Sam James
2024-05-28 13:19 Sam James
2024-04-21 6:04 Markus Meier
2023-04-29 20:31 Sam James
2023-04-29 20:25 Sam James
2023-04-29 20:25 Sam James
2023-04-29 20:20 Sam James
2023-04-29 18:16 Arthur Zamarin
2023-04-29 18:04 Arthur Zamarin
2023-02-07 18:01 Andreas Sturmlechner
2022-12-22 20:05 Andreas Sturmlechner
2022-12-21 0:19 Sam James
2022-12-20 23:57 Sam James
2022-12-20 23:57 Sam James
2022-12-20 23:29 Sam James
2022-12-20 23:29 Sam James
2022-12-20 23:28 Sam James
2022-12-20 23:28 Sam James
2022-12-01 3:21 WANG Xuerui
2022-03-05 22:39 Andreas K. Hüttel
2022-02-28 23:17 Andreas K. Hüttel
2021-02-27 21:12 Andreas K. Hüttel
2020-06-18 17:54 Markus Meier
2020-06-06 23:18 Andreas K. Hüttel
2020-04-25 12:37 Andreas Sturmlechner
2019-10-06 13:27 Alexey Shvetsov
2019-05-21 6:31 Aaron Bauman
2018-05-20 19:10 Andreas Sturmlechner
2018-04-15 17:15 Andreas Sturmlechner
2018-04-07 12:05 Sergei Trofimovich
2018-04-02 8:33 Markus Meier
2018-04-01 11:08 Sergei Trofimovich
2018-03-31 10:58 Sergei Trofimovich
2018-03-05 10:36 Tobias Klausmann
2018-03-02 14:15 Jason Zaman
2018-02-27 16:48 Markus Meier
2018-02-24 9:41 Sergei Trofimovich
2017-12-25 23:14 Andreas Sturmlechner
2017-06-18 9:51 Alexis Ballier
2017-05-28 9:26 Markus Meier
2016-01-11 9:07 Agostino Sarubbo
2016-01-09 6:43 Agostino Sarubbo
2015-12-07 11:40 Agostino Sarubbo
2015-12-05 10:12 Jeroen Roovers
2015-12-05 10:12 Jeroen Roovers
2015-12-03 13:28 Agostino Sarubbo
2015-11-29 19:08 Markus Meier
2015-11-23 9:25 Agostino Sarubbo
2015-11-23 8:50 Agostino Sarubbo
2015-11-21 14:34 Markus Meier
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=1682799916.78b3e02553027b32f1c461cb48ec3f6661ad1103.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