Github messages for voidlinux
 help / color / mirror / Atom feed
From: dataCobra <dataCobra@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] clamav: update to 0.103.8.
Date: Thu, 02 Mar 2023 08:26:15 +0100	[thread overview]
Message-ID: <20230302072615.KnxT8kG0BE3i2oiokBz8ZUM5iF7B8ZiSoBtR8HKyuYg@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42544@inbox.vuxu.org>

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

There is an updated pull request by dataCobra against master on the void-packages repository

https://github.com/dataCobra/void-packages clamav
https://github.com/void-linux/void-packages/pull/42544

clamav: update to 0.103.8.
#### Testing the changes
- I tested the changes in this PR: **briefly**

#### 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 (crossbuild)
  - armv7l (crossbuild)
  - armv6l-musl (crossbuild)

This release contains very important fixes for some critical CVEs.
Here is the information: https://blog.clamav.net/

We should merge this PR ASAP.

A patch file from https://github.com/void-linux/void-packages/pull/42544.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-clamav-42544.patch --]
[-- Type: text/x-diff, Size: 1271 bytes --]

From 17640947b9880118d98f86e6d9df1d72d3c37f8c Mon Sep 17 00:00:00 2001
From: dataCobra <datacobra@thinkbot.de>
Date: Thu, 2 Mar 2023 08:26:00 +0100
Subject: [PATCH] clamav: update to 0.103.8.

---
 srcpkgs/clamav/template | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/srcpkgs/clamav/template b/srcpkgs/clamav/template
index 6fbc98e326cf..a526f8dfa08f 100644
--- a/srcpkgs/clamav/template
+++ b/srcpkgs/clamav/template
@@ -1,7 +1,7 @@
 # Template file for 'clamav'
 pkgname=clamav
-version=0.103.4
-revision=3
+version=0.103.8
+revision=1
 build_style=gnu-configure
 # XXX: system llvm is too new (< 3.7 required)
 # Shipped llvm does not build with gcc>=6
@@ -19,11 +19,11 @@ maintainer="Orphaned <orphan@voidlinux.org>"
 license="GPL-2.0-only"
 homepage="https://www.clamav.net/"
 distfiles="https://www.clamav.net/downloads/production/clamav-${version}.tar.gz"
-checksum=def0ad15500fa6aff81d8e68b9f83aa75ee5b607a01335c1d26dbcc959932f85
+checksum=6f49da6ee927936de13d359e559d3944248e3a257d40b80b6c99ebe6fe8c8c3f
 _clamav_homedir="/var/lib/_${pkgname}"
 _clamav_descr="ClamAV user"
 system_accounts="_clamav"
-make_check=ci-skip
+make_check=ci-skip # I've no idea why...
 
 CPPFLAGS="-Wno-unused-local-typedefs"
 if [ "$CROSS_BUILD" ]; then

  reply	other threads:[~2023-03-02  7:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-02  7:23 [PR PATCH] " dataCobra
2023-03-02  7:26 ` dataCobra [this message]
2023-03-02  7:31 ` [PR REVIEW] " the-maldridge
2023-03-02  7:33 ` dataCobra
2023-03-02  7:35 ` [PR PATCH] [Updated] " dataCobra
2023-03-02  7:36 ` [PR REVIEW] " dataCobra
2023-03-02  7:37 ` [PR PATCH] [Merged]: " the-maldridge

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=20230302072615.KnxT8kG0BE3i2oiokBz8ZUM5iF7B8ZiSoBtR8HKyuYg@z \
    --to=datacobra@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).