mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Christian Melki <christian.melki@t2data.com>
Subject: Re: [ptxdist] [APPLIED] libarchive: Version bump. 3.5.1 -> 3.6.1
Date: Wed, 25 May 2022 11:45:10 +0200	[thread overview]
Message-ID: <20220525094510.2845232-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20220510200100.3831734-1-christian.melki@t2data.com>

Thanks, applied as 8ea88e6dfb1890a814390347d66d1d898791f0f9.

Michael

[sent from post-receive hook]

On Wed, 25 May 2022 11:45:10 +0200, Christian Melki <christian.melki@t2data.com> wrote:
> Various bugfixes over the last year.
> Fixes CVE-2021-31566, CVE-2021-36976 and
> plugs various other detected security issues.
> 
> https://github.com/libarchive/libarchive/releases
> 
> Signed-off-by: Christian Melki <christian.melki@t2data.com>
> Message-Id: <20220510200100.3831734-1-christian.melki@t2data.com>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
> 
> diff --git a/rules/libarchive.make b/rules/libarchive.make
> index 11a7586cc0cc..e75034d74fea 100644
> --- a/rules/libarchive.make
> +++ b/rules/libarchive.make
> @@ -14,8 +14,8 @@ PACKAGES-$(PTXCONF_LIBARCHIVE) += libarchive
>  #
>  # Paths and names
>  #
> -LIBARCHIVE_VERSION	:= 3.5.1
> -LIBARCHIVE_MD5		:= c96040b75a14c8ba73238c284147e87f
> +LIBARCHIVE_VERSION	:= 3.6.1
> +LIBARCHIVE_MD5		:= 802a56ef9eaa0b8776296ba78a6d0c2c
>  LIBARCHIVE		:= libarchive-$(LIBARCHIVE_VERSION)
>  LIBARCHIVE_SUFFIX	:= tar.gz
>  LIBARCHIVE_URL		:= https://www.libarchive.org/downloads/$(LIBARCHIVE).$(LIBARCHIVE_SUFFIX)



      reply	other threads:[~2022-05-25  9:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-10 20:01 [ptxdist] [PATCH] " Christian Melki
2022-05-25  9:45 ` Michael Olbrich [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=20220525094510.2845232-1-m.olbrich@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=christian.melki@t2data.com \
    --cc=ptxdist@pengutronix.de \
    /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