Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Perez de Castro <aperez@igalia.com>
To: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/wpebackend-fdo: bump to version 1.16.1
Date: Sat, 20 Dec 2025 00:50:03 +0200	[thread overview]
Message-ID: <20251220005003.GD762893@igalia.com> (raw)
In-Reply-To: <20251219164127.3999273-1-aperez@igalia.com>


[-- Attachment #1.1: Type: text/plain, Size: 2326 bytes --]

Hi,

On Fri, 19 Dec 2025 18:41:25 +0200 Adrian Perez de Castro <aperez@igalia.com> wrote:
> This maintenance release introduces support for newer versions of the
> Mesa library. Release notes:
> 
>   https://wpewebkit.org/release/wpebackend-fdo-1.16.1.html
> 
> Signed-off-by: Adrian Perez de Castro <aperez@igalia.com>

Do not merge this yet, I have found at least one configuration where
the updated package fails to build due to a missing #include. I'll add
a patch for it.



> ---
>  package/wpebackend-fdo/wpebackend-fdo.hash | 8 ++++----
>  package/wpebackend-fdo/wpebackend-fdo.mk   | 2 +-
>  2 files changed, 5 insertions(+), 5 deletions(-)
> 
> diff --git a/package/wpebackend-fdo/wpebackend-fdo.hash b/package/wpebackend-fdo/wpebackend-fdo.hash
> index f0578808c4..5e36137524 100644
> --- a/package/wpebackend-fdo/wpebackend-fdo.hash
> +++ b/package/wpebackend-fdo/wpebackend-fdo.hash
> @@ -1,7 +1,7 @@
> -# From https://wpewebkit.org/releases/wpebackend-fdo-1.16.0.tar.xz.sums
> -md5  38f488aaa6d68252b593b65ba3e2d9d1  wpebackend-fdo-1.16.0.tar.xz
> -sha1  8a06e51aeb2c94b4cf254d866c19eca587d3cd37  wpebackend-fdo-1.16.0.tar.xz
> -sha256  beddf321232d5bd08106c179dbc600f8ce88eb3620b4a59a6329063b78f64635  wpebackend-fdo-1.16.0.tar.xz
> +# From https://wpewebkit.org/releases/wpebackend-fdo-1.16.1.tar.xz.sums
> +md5  a112358168e03abf4937c0cecfe1dc9d  wpebackend-fdo-1.16.1.tar.xz
> +sha1  4ed9d1d568ef805f79b691baa0d1cbdff17ef453  wpebackend-fdo-1.16.1.tar.xz
> +sha256  544ae14012f8e7e426b8cb522eb0aaaac831ad7c35601d1cf31d37670e0ebb3b  wpebackend-fdo-1.16.1.tar.xz
>  
>  # Hashes for license files:
>  sha256  c9f6803371047fad3e72200ec6cd226329a5ee08ac61104c8211c2761fb46825  COPYING
> diff --git a/package/wpebackend-fdo/wpebackend-fdo.mk b/package/wpebackend-fdo/wpebackend-fdo.mk
> index e5972754f6..6dbe6edfe3 100644
> --- a/package/wpebackend-fdo/wpebackend-fdo.mk
> +++ b/package/wpebackend-fdo/wpebackend-fdo.mk
> @@ -4,7 +4,7 @@
>  #
>  ################################################################################
>  
> -WPEBACKEND_FDO_VERSION = 1.16.0
> +WPEBACKEND_FDO_VERSION = 1.16.1
>  WPEBACKEND_FDO_SITE = https://wpewebkit.org/releases
>  WPEBACKEND_FDO_SOURCE = wpebackend-fdo-$(WPEBACKEND_FDO_VERSION).tar.xz
>  WPEBACKEND_FDO_INSTALL_STAGING = YES
> -- 
> 2.52.0
> 
> 

Cheers,
—Adrián

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 150 bytes --]

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2025-12-19 22:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-19 16:41 [Buildroot] [PATCH] package/wpebackend-fdo: bump to version 1.16.1 Adrian Perez de Castro
2025-12-19 22:50 ` Adrian Perez de Castro [this message]

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=20251220005003.GD762893@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