From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, master, updated. 1a200cffc994858c8cad91b9b00093d24f00e79a
Date: Sun, 11 May 2014 19:02:29 +0200 [thread overview]
Message-ID: <20140511170229.B9CA1210F2@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 3178 bytes --]
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "IPFire 2.x development tree".
The branch, master has been updated
via 1a200cffc994858c8cad91b9b00093d24f00e79a (commit)
from 03fa5cba13c77b0a4ee8a1e84bf895af113ecb26 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit 1a200cffc994858c8cad91b9b00093d24f00e79a
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Sun May 11 19:01:45 2014 +0200
clamav: update to 0.98.3.
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/packages/clamav | 8 +++++---
lfs/clamav | 7 ++++---
2 files changed, 9 insertions(+), 6 deletions(-)
Difference in files:
diff --git a/config/rootfiles/packages/clamav b/config/rootfiles/packages/clamav
index 885af45..e27eba6 100644
--- a/config/rootfiles/packages/clamav
+++ b/config/rootfiles/packages/clamav
@@ -4,21 +4,22 @@ usr/bin/clamconf
usr/bin/clamdscan
usr/bin/clamdtop
usr/bin/clamscan
+usr/bin/clamsubmit
usr/bin/freshclam
usr/bin/sigtool
#usr/include/clamav.h
#usr/lib/libclamav.la
usr/lib/libclamav.so
usr/lib/libclamav.so.6
-usr/lib/libclamav.so.6.1.20
+usr/lib/libclamav.so.6.1.22
#usr/lib/libclamunrar.la
usr/lib/libclamunrar.so
usr/lib/libclamunrar.so.6
-usr/lib/libclamunrar.so.6.1.20
+usr/lib/libclamunrar.so.6.1.22
#usr/lib/libclamunrar_iface.la
usr/lib/libclamunrar_iface.so
usr/lib/libclamunrar_iface.so.6
-usr/lib/libclamunrar_iface.so.6.1.20
+usr/lib/libclamunrar_iface.so.6.1.22
#usr/lib/pkgconfig/libclamav.pc
usr/sbin/clamd
usr/share/clamav
@@ -27,6 +28,7 @@ usr/share/clamav
#usr/share/man/man1/clamdscan.1
#usr/share/man/man1/clamdtop.1
#usr/share/man/man1/clamscan.1
+#usr/share/man/man1/clamsubmit.1
#usr/share/man/man1/freshclam.1
#usr/share/man/man1/sigtool.1
#usr/share/man/man5/clamav-milter.conf.5
diff --git a/lfs/clamav b/lfs/clamav
index 4a9a5a2..8cb849b 100644
--- a/lfs/clamav
+++ b/lfs/clamav
@@ -24,7 +24,7 @@
include Config
-VER = 0.98.1
+VER = 0.98.3
THISAPP = clamav-$(VER)
DL_FILE = $(THISAPP).tar.gz
@@ -32,7 +32,7 @@ DL_FROM = $(URL_IPFIRE)
DIR_APP = $(DIR_SRC)/$(THISAPP)
TARGET = $(DIR_INFO)/$(THISAPP)
PROG = clamav
-PAK_VER = 24
+PAK_VER = 25
DEPS = ""
@@ -48,7 +48,7 @@ objects = $(DL_FILE)
$(DL_FILE) = $(DL_FROM)/$(DL_FILE)
-$(DL_FILE)_MD5 = b1ec7b19dea8385954515ef1d63576d8
+$(DL_FILE)_MD5 = b649d35ee85d4d6075a98173dd255c17
install : $(TARGET)
@@ -96,6 +96,7 @@ $(TARGET) : $(patsubst %,$(DIR_DL)/%,$(objects))
# Disable PaX mprotect for clamd and freshclam
paxctl -cm /usr/sbin/clamd
+ paxctl -cm /usr/bin/clamscan
paxctl -cm /usr/bin/freshclam
@rm -rf $(DIR_APP)
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2014-05-11 17:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20140511170229.B9CA1210F2@argus.ipfire.org \
--to=git@ipfire.org \
--cc=ipfire-scm@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