From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] fribidi: Update to version 1.0.12
Date: Sat, 23 Apr 2022 14:47:32 +0000 [thread overview]
Message-ID: <19db662f-2d1b-563e-88c5-e6339fa7d840@ipfire.org> (raw)
In-Reply-To: <20220423111716.3587997-1-adolf.belka@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1313 bytes --]
Reviewed-by: Peter Müller <peter.mueller(a)ipfire.org>
> - Update from 1.0.11 to 1.0.12
> - Update of rootfile not required
> - Changelog
> Overview of changes between 1.0.11 and 1.0.12
> * Various fuzzing fixes.
> - Looking at the details in the commits it looks like fribidi's use of the word fuzzing
> fixes basically means bug fixes. Included are fixes for a segmentation violation and a
> stack buffer overflow
>
> Signed-off-by: Adolf Belka <adolf.belka(a)ipfire.org>
> ---
> lfs/fribidi | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/lfs/fribidi b/lfs/fribidi
> index e9c362788..75ea2d148 100644
> --- a/lfs/fribidi
> +++ b/lfs/fribidi
> @@ -24,7 +24,7 @@
>
> include Config
>
> -VER = 1.0.11
> +VER = 1.0.12
>
> THISAPP = fribidi-$(VER)
> DL_FILE = $(THISAPP).tar.xz
> @@ -40,7 +40,7 @@ objects = $(DL_FILE)
>
> $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
>
> -$(DL_FILE)_BLAKE2 = 9de3e170e2b6cf90623c711e16f6595f6ca91e14707cbfd36dda7df92689ea79ec36c4b658199e9046eedd07c9ebfde18617525c83cf4b0e9e2ccb4d9f82ed84
> +$(DL_FILE)_BLAKE2 = f76f9d28f738f0cc9790ccdf0fe419cb0e7d70b24aa825844d23c4b31ad51c33f09c88ad4876fa6a52523f2a52d5eb7a4b50deeb70f9db750c69ac236ecfa8f5
>
> install : $(TARGET)
>
prev parent reply other threads:[~2022-04-23 14:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-23 11:17 Adolf Belka
2022-04-23 14:47 ` Peter Müller [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=19db662f-2d1b-563e-88c5-e6339fa7d840@ipfire.org \
--to=peter.mueller@ipfire.org \
--cc=development@lists.ipfire.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