public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: media-libs/libde265/
Date: Tue,  7 Sep 2021 03:05:35 +0000 (UTC)	[thread overview]
Message-ID: <1630983924.5903c93fa672a9165ab106d6d913b7e22be048d0.sam@gentoo> (raw)

commit:     5903c93fa672a9165ab106d6d913b7e22be048d0
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Tue Sep  7 03:05:24 2021 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Tue Sep  7 03:05:24 2021 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=5903c93f

media-libs/libde265: Stabilize 1.0.8 ppc64, #783555

Signed-off-by: Sam James <sam <AT> gentoo.org>

 media-libs/libde265/libde265-1.0.8.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/media-libs/libde265/libde265-1.0.8.ebuild b/media-libs/libde265/libde265-1.0.8.ebuild
index a8e64d68e74..057bfb6eff5 100644
--- a/media-libs/libde265/libde265-1.0.8.ebuild
+++ b/media-libs/libde265/libde265-1.0.8.ebuild
@@ -10,7 +10,7 @@ if [[ ${PV} == *9999 ]] ; then
 	inherit git-r3
 else
 	SRC_URI="https://github.com/strukturag/${PN}/archive/v${PV}.tar.gz -> ${P}.tar.gz"
-	KEYWORDS="amd64 arm arm64 ~ppc64 ~riscv x86"
+	KEYWORDS="amd64 arm arm64 ppc64 ~riscv x86"
 fi
 
 DESCRIPTION="Open h.265 video codec implementation"


             reply	other threads:[~2021-09-07  3:05 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-07  3:05 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-08-10 15:41 [gentoo-commits] repo/gentoo:master commit in: media-libs/libde265/ Michał Górny
2024-08-09  8:50 Jakov Smolić
2024-08-05 11:35 Jakov Smolić
2024-08-05 10:34 Jakov Smolić
2024-08-05 10:34 Jakov Smolić
2024-05-03 11:20 Sam James
2024-05-03 11:20 Sam James
2023-10-23  4:14 John Helmert III
2023-04-26  4:03 Sam James
2023-04-26  3:53 Sam James
2023-04-26  3:53 Sam James
2023-04-26  3:53 Sam James
2023-04-26  3:53 Sam James
2023-03-11  4:34 John Helmert III
2023-01-06  8:10 Sam James
2023-01-06  1:27 Sam James
2023-01-05 23:48 Sam James
2023-01-05 23:48 Sam James
2023-01-05 20:31 Arthur Zamarin
2022-11-04  2:24 Sam James
2022-05-25  9:10 WANG Xuerui
2022-05-25  9:10 WANG Xuerui
2021-04-25  9:31 Sam James
2021-02-13 20:59 Conrad Kostecki
2021-02-13 19:18 Sam James
2021-02-03  0:01 Sam James
2021-02-01 13:33 Sam James
2020-12-29 13:38 David Seifert
2020-12-29 13:38 David Seifert
2020-11-12 15:17 Sam James
2020-11-12  6:51 Joonas Niilola
2020-11-12  0:35 Thomas Deutschmann
2020-07-30  3:50 Sam James
2020-07-27 15:09 Craig Andrews
2020-04-26  9:21 Mikle Kolyada
2019-12-26 12:56 Georgy Yakovlev
2019-12-26 12:56 Georgy Yakovlev
2019-07-24 23:09 Aaron Bauman
2018-09-21 12:41 Thomas Deutschmann
2018-09-21  7:41 Agostino Sarubbo
2018-09-19 17:35 Thomas Deutschmann
2018-09-12 13:49 Andreas Sturmlechner
2018-09-12 13:32 Andreas Sturmlechner
2018-09-08 22:04 Thomas Deutschmann
2017-11-20 19:56 Andreas Sturmlechner
2017-11-20 19:56 Andreas Sturmlechner
2017-07-30  9:38 Michał Górny
2016-12-07  7:39 Yixun Lan
2016-12-05  7:58 Yixun Lan
2015-11-09  3:03 Yixun Lan

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=1630983924.5903c93fa672a9165ab106d6d913b7e22be048d0.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