From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. c99b595f5725750d377040ab5b03de7b3ab80d8f
Date: Sat, 09 Mar 2013 18:53:21 +0100 [thread overview]
Message-ID: <20130309175321.A179E200F8@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1665 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, next has been updated
via c99b595f5725750d377040ab5b03de7b3ab80d8f (commit)
from 223fddd97a0f8c58322788f3e0fb6eb2eb7772cf (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 c99b595f5725750d377040ab5b03de7b3ab80d8f
Author: Thomas Ebert <thomas.ebert(a)ipfire.org>
Date: Fri Mar 8 18:18:58 2013 +0100
squidclamav: updated to 5.11.
-----------------------------------------------------------------------
Summary of changes:
lfs/squidclamav | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
Difference in files:
diff --git a/lfs/squidclamav b/lfs/squidclamav
index 8fcc3c2..86255f8 100644
--- a/lfs/squidclamav
+++ b/lfs/squidclamav
@@ -24,7 +24,7 @@
include Config
-VER = 5.7
+VER = 5.11
THISAPP = squidclamav-$(VER)
DL_FILE = $(THISAPP).tar.gz
@@ -32,7 +32,7 @@ DL_FROM = $(URL_IPFIRE)
DIR_APP = $(DIR_SRC)/$(THISAPP)
TARGET = $(DIR_INFO)/$(THISAPP)
PROG = squidclamav
-PAK_VER = 14
+PAK_VER = 15
DEPS = "clamav"
@@ -44,7 +44,7 @@ objects = $(DL_FILE)
$(DL_FILE) = $(DL_FROM)/$(DL_FILE)
-$(DL_FILE)_MD5 = 02207a95e2968998574e30d35e0d1f0e
+$(DL_FILE)_MD5 = 87aef2eb48a41fa1e466c0174f2bac40
install : $(TARGET)
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2013-03-09 17:53 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=20130309175321.A179E200F8@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