public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] clamav: Update to 0.105.1
Date: Wed, 27 Jul 2022 08:16:41 +0100	[thread overview]
Message-ID: <4AE0B6F4-6038-4FD8-A62E-CF059CB24F9F@ipfire.org> (raw)
In-Reply-To: <20220727000005.3514229-1-matthias.fischer@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 2797 bytes --]

Hello,

Oh this sounds like a really bad one. I’ve merged it straight away.

Thanks for working on this so swiftly :)

-Michael

> On 27 Jul 2022, at 01:00, Matthias Fischer <matthias.fischer(a)ipfire.org> wrote:
> 
> For details see:
> https://blog.clamav.net/2022/07/clamav-01037-01041-and-01051-patch.html
> 
> "ClamAV 0.105.1 is a critical patch release with the following fixes:
> 
>    Upgrade the vendored UnRAR library to version 6.1.7.
> 
>    Fix issue building macOS universal binaries in some configurations.
> 
>    Silence error message when the logical signature maximum functionality
>    level is lower than the current functionality level.
> 
>    Fix scan error when scanning files containing malformed images that
>    cannot be loaded to calculate an image fuzzy hash.
> 
>    Fix logical signature "Intermediates" feature.
> 
>    Relax constraints on slightly malformed ZIP archives that contain
>    overlapping file entries."
> 
> Signed-off-by: Matthias Fischer <matthias.fischer(a)ipfire.org>
> ---
> config/rootfiles/packages/clamav | 1 +
> lfs/clamav                       | 6 +++---
> 2 files changed, 4 insertions(+), 3 deletions(-)
> 
> diff --git a/config/rootfiles/packages/clamav b/config/rootfiles/packages/clamav
> index ca3124bb2..588c34eb4 100644
> --- a/config/rootfiles/packages/clamav
> +++ b/config/rootfiles/packages/clamav
> @@ -56,6 +56,7 @@ usr/sbin/clamd
> #usr/share/doc/ClamAV/html/clipboard.min.js
> #usr/share/doc/ClamAV/html/community_resources
> #usr/share/doc/ClamAV/html/community_resources/CommunityResources.html
> +#usr/share/doc/ClamAV/html/community_resources/CompileClamAV_AmazonLinux2.txt
> #usr/share/doc/ClamAV/html/css
> #usr/share/doc/ClamAV/html/css/chrome.css
> #usr/share/doc/ClamAV/html/css/general.css
> diff --git a/lfs/clamav b/lfs/clamav
> index 1a4913089..bcb996c4f 100644
> --- a/lfs/clamav
> +++ b/lfs/clamav
> @@ -26,7 +26,7 @@ include Config
> 
> SUMMARY    = Antivirus Toolkit
> 
> -VER        = 0.105.0
> +VER        = 0.105.1
> 
> THISAPP    = clamav-$(VER)
> DL_FILE    = $(THISAPP).tar.gz
> @@ -34,7 +34,7 @@ DL_FROM    = $(URL_IPFIRE)
> DIR_APP    = $(DIR_SRC)/$(THISAPP)
> TARGET     = $(DIR_INFO)/$(THISAPP)
> PROG       = clamav
> -PAK_VER    = 60
> +PAK_VER    = 61
> 
> DEPS       =
> 
> @@ -50,7 +50,7 @@ objects = $(DL_FILE)
> 
> $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
> 
> -$(DL_FILE)_BLAKE2 = 2c3055c3c5de115e01b6c0decee21c061c0583171c1794a38ecd86f354765879a6a2b7f2653c67fc19273dfc0caa9da8a2bbe339854e4c0d237baf3f3c650813
> +$(DL_FILE)_BLAKE2 = be46d9afd76fb536d7de7363a45d38fef6a5983011e3cd0dcc25c2a209c8d37a2bbe1f7f4a5694152cabf622ef83e072b892ae12ba404da1955bb5b654e5216d
> 
> install : $(TARGET)
> 
> -- 
> 2.25.1
> 


      reply	other threads:[~2022-07-27  7:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-27  0:00 Matthias Fischer
2022-07-27  7:16 ` Michael Tremer [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=4AE0B6F4-6038-4FD8-A62E-CF059CB24F9F@ipfire.org \
    --to=michael.tremer@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