public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Arthur Zamarin" <arthurzam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: media-libs/libavif/
Date: Wed,  5 Jan 2022 17:34:48 +0000 (UTC)	[thread overview]
Message-ID: <1641404078.b09768fc89c375b4f94068ec85cc692bbcff8856.arthurzam@gentoo> (raw)

commit:     b09768fc89c375b4f94068ec85cc692bbcff8856
Author:     Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
AuthorDate: Wed Jan  5 17:34:30 2022 +0000
Commit:     Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
CommitDate: Wed Jan  5 17:34:38 2022 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b09768fc

media-libs/libavif: Stabilize 0.9.3-r1 ppc64, #827896

Signed-off-by: Arthur Zamarin <arthurzam <AT> gentoo.org>

 media-libs/libavif/libavif-0.9.3-r1.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/media-libs/libavif/libavif-0.9.3-r1.ebuild b/media-libs/libavif/libavif-0.9.3-r1.ebuild
index bcf2e84bf548..fcbde27db210 100644
--- a/media-libs/libavif/libavif-0.9.3-r1.ebuild
+++ b/media-libs/libavif/libavif-0.9.3-r1.ebuild
@@ -13,7 +13,7 @@ SRC_URI="https://github.com/AOMediaCodec/libavif/archive/v${PV}.tar.gz -> ${P}.t
 LICENSE="BSD-2"
 # See bug #822336 re subslot
 SLOT="0/${PV}"
-KEYWORDS="amd64 arm arm64 ~ppc64 ~riscv x86"
+KEYWORDS="amd64 arm arm64 ppc64 ~riscv x86"
 IUSE="+aom dav1d examples extras gdk-pixbuf rav1e svt-av1"
 
 REQUIRED_USE="|| ( aom dav1d )"


             reply	other threads:[~2022-01-05 17:34 UTC|newest]

Thread overview: 73+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-05 17:34 Arthur Zamarin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-10-04 17:37 [gentoo-commits] repo/gentoo:master commit in: media-libs/libavif/ Andreas Sturmlechner
2024-09-24 15:22 Sam James
2024-09-23  7:32 Arthur Zamarin
2024-09-23  7:32 Arthur Zamarin
2024-09-23  7:13 Arthur Zamarin
2024-09-23  7:13 Arthur Zamarin
2024-09-23  5:56 Sam James
2024-08-13  4:55 Michał Górny
2024-08-01  6:28 Joonas Niilola
2024-08-01  6:28 Joonas Niilola
2024-08-01  6:28 Joonas Niilola
2024-08-01  6:28 Joonas Niilola
2024-04-03 17:44 Michał Górny
2024-03-23  5:40 Michał Górny
2024-03-23  5:40 Michał Górny
2024-02-06 11:02 Michał Górny
2024-02-02 17:11 Michał Górny
2024-01-23  5:07 Ionen Wolkens
2024-01-09 14:38 Joonas Niilola
2024-01-09 14:38 Joonas Niilola
2023-12-25 17:26 Sam James
2023-12-12  6:30 Viorel Munteanu
2023-11-23 17:12 Sam James
2023-11-22 17:13 Florian Schmaus
2023-10-06  8:29 Joonas Niilola
2023-10-06  8:29 Joonas Niilola
2022-11-12  7:00 Joonas Niilola
2022-10-18 10:23 Agostino Sarubbo
2022-10-18  5:42 Sam James
2022-10-17 17:26 Arthur Zamarin
2022-08-05  7:16 Agostino Sarubbo
2022-08-04  8:03 Agostino Sarubbo
2022-05-17 11:54 WANG Xuerui
2022-04-18  7:27 Joonas Niilola
2022-03-22 17:02 Sam James
2022-01-03  9:20 Sam James
2022-01-03  9:19 Sam James
2022-01-02 22:51 Sam James
2022-01-02 22:50 Sam James
2021-11-07 23:08 Sam James
2021-10-24  4:06 Sam James
2021-10-24  4:06 Sam James
2021-09-07  3:05 Sam James
2021-09-07  3:03 Sam James
2021-08-02 16:42 Marek Szuba
2021-06-30  6:53 Joonas Niilola
2021-05-23 23:07 Thomas Deutschmann
2021-05-23 12:12 Andreas Sturmlechner
2021-05-16 20:00 Sam James
2021-04-25  9:31 Sam James
2021-03-11 17:26 Sam James
2021-03-11  8:52 Joonas Niilola
2021-03-05  5:38 Joonas Niilola
2021-02-28 10:56 Joonas Niilola
2021-02-15  6:05 Sam James
2021-02-12 16:20 Sam James
2021-02-04  8:12 Agostino Sarubbo
2021-02-03  3:12 Sam James
2021-01-15  8:44 Joonas Niilola
2020-11-26  7:53 Joonas Niilola
2020-11-25 11:29 Joonas Niilola
2020-11-12  7:28 Joonas Niilola
2020-11-12  7:28 Joonas Niilola
2020-11-10 17:27 Joonas Niilola
2020-11-10 17:27 Joonas Niilola
2020-10-17 16:46 Joonas Niilola
2020-10-01 22:29 Sergei Trofimovich
2020-09-29 11:40 Sam James
2020-09-27 19:28 Sam James
2020-09-27 10:27 Joonas Niilola
2020-09-25 13:49 Joonas Niilola
2020-09-25  9:34 Joonas Niilola

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=1641404078.b09768fc89c375b4f94068ec85cc692bbcff8856.arthurzam@gentoo \
    --to=arthurzam@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