From: Adrian Perez de Castro <aperez@igalia.com>
To: buildroot@buildroot.org
Cc: Adrian Perez de Castro <aperez@igalia.com>
Subject: [Buildroot] [PATCH] package/libavif: bump version to 1.4.1
Date: Fri, 17 Apr 2026 11:06:45 +0300 [thread overview]
Message-ID: <20260417080647.1404627-1-aperez@igalia.com> (raw)
Release notes:
https://github.com/AOMediaCodec/libavif/releases/tag/v1.4.0
https://github.com/AOMediaCodec/libavif/releases/tag/v1.4.1
Signed-off-by: Adrian Perez de Castro <aperez@igalia.com>
---
package/libavif/libavif.hash | 2 +-
package/libavif/libavif.mk | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/package/libavif/libavif.hash b/package/libavif/libavif.hash
index c53e0c9f50..4f9d899d27 100644
--- a/package/libavif/libavif.hash
+++ b/package/libavif/libavif.hash
@@ -1,3 +1,3 @@
-sha256 0a545e953cc049bf5bcf4ee467306a2f113a75110edf59e61248873101cd26c1 libavif-1.3.0.tar.gz
+sha256 d4aea31a4becb3273ba7968221be2e48148ba05eb8a68d14e671963e17785648 libavif-1.4.1.tar.gz
sha256 165abf92cc04b39e80d29cadea7a6a7e8fddf59407d4ad2616507a7ebe8216f9 LICENSE
diff --git a/package/libavif/libavif.mk b/package/libavif/libavif.mk
index 4357566ed1..8bd130fd65 100644
--- a/package/libavif/libavif.mk
+++ b/package/libavif/libavif.mk
@@ -4,7 +4,7 @@
#
################################################################################
-LIBAVIF_VERSION = 1.3.0
+LIBAVIF_VERSION = 1.4.1
LIBAVIF_SITE = $(call github,AOMediaCodec,libavif,v$(LIBAVIF_VERSION))
LIBAVIF_LICENSE = BSD-2-Clause, IJG, Apache-2.0
LIBAVIF_LICENSE_FILES = LICENSE
--
2.53.0
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2026-04-17 8:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-17 8:06 Adrian Perez de Castro [this message]
2026-04-19 21:23 ` [Buildroot] [PATCH] package/libavif: bump version to 1.4.1 Julien Olivain via buildroot
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=20260417080647.1404627-1-aperez@igalia.com \
--to=aperez@igalia.com \
--cc=buildroot@buildroot.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