From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: New package for 'clamav 0.105.1(-2) necessary?
Date: Mon, 07 Nov 2022 16:55:47 +0000 [thread overview]
Message-ID: <84FC8188-7A20-49EF-95E4-4BC09A872000@ipfire.org> (raw)
In-Reply-To: <e9920d0d-5dd9-5af7-0de6-25510c4bae8c@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1038 bytes --]
What he said!
> On 7 Nov 2022, at 10:48, Peter Müller <peter.mueller(a)ipfire.org> wrote:
>
> Hello Matthias,
>
> thanks for raising this.
>
> Yes, please. Keep the package updates coming, highly appreciated. :-)
>
> All the best,
> Peter Müller
>
>> Hi,
>>
>> short question, based on
>> https://blog.clamav.net/2022/10/new-packages-for-clamav-01037-01044.html
>>
>> Excerpt:
>> "...there are several critical bugs in the JPEG and TIFF image
>> processing libraries in the original 0.105.1 source package. The known
>> issues were resolved in image-tiff version 0.7.4 and jpeg-decoder
>> version 0.3.0. The clamav-0.105.1-2.tar.gz source package includes the
>> updated libraries.
>> Linux/Unix package maintainers are encouraged to publish new revisions
>> of their own packages for ClamAV 0.105.1 to get these fixes. Anyone who
>> built ClamAV from the original clamav-0.105.1.tar.gz source package is
>> encouraged to reinstall from the newer source package."
>>
>> Do we want an updated package?
>>
>> Best,
>> Matthias
prev parent reply other threads:[~2022-11-07 16:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-07 10:21 Matthias Fischer
2022-11-07 10:48 ` Peter Müller
2022-11-07 16:55 ` 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=84FC8188-7A20-49EF-95E4-4BC09A872000@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