From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: clamav: update to 0.103.4
Date: Sun, 19 Dec 2021 02:00:24 +0100 [thread overview]
Message-ID: <20211219010024.VskI5eDPiTzlFooFMc6ITIQkd9hspq9BvIym43cxeLo@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34567@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1168 bytes --]
There's a merged pull request on the void-packages repository
clamav: update to 0.103.4
https://github.com/void-linux/void-packages/pull/34567
Description:
- changelog for our LTS version : https://blog.clamav.net/2021/11/clamav-01034-and-01041-patch-releases.html
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**
<!--
#### New package
- This new package conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements): **YES**
-->
<!-- Note: If the build is likely to take more than 2 hours, please [skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration)
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
<!--
#### Local build testing
- I built this PR locally for my native architecture, (x86_64-glibc)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- aarch64-musl [OK]
- x86_64-musl [OK]
-->
prev parent reply other threads:[~2021-12-19 1:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-16 12:35 [PR PATCH] " biopsin
2021-12-17 8:31 ` ericonr
2021-12-18 12:59 ` [PR PATCH] [Updated] " biopsin
2021-12-18 13:00 ` biopsin
2021-12-18 13:01 ` biopsin
2021-12-18 13:02 ` biopsin
2021-12-19 1:00 ` ericonr [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=20211219010024.VskI5eDPiTzlFooFMc6ITIQkd9hspq9BvIym43cxeLo@z \
--to=ericonr@users.noreply.github.com \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).