From: Arne Fitzenreiter <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 912c590bb61d7d84893ee4b7f382f9eba0463b8f
Date: Sun, 04 Nov 2018 07:42:52 +0000 [thread overview]
Message-ID: <20181104074252.A17D01081BB0@git01.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1517 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 912c590bb61d7d84893ee4b7f382f9eba0463b8f (commit)
from e9dbafa8a13e695a2d257f44d1e66468847aa891 (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 912c590bb61d7d84893ee4b7f382f9eba0463b8f
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Sun Nov 4 08:41:43 2018 +0100
clamav: fix rootfile
Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/packages/clamav | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
Difference in files:
diff --git a/config/rootfiles/packages/clamav b/config/rootfiles/packages/clamav
index 3f872f317..2be31d5db 100644
--- a/config/rootfiles/packages/clamav
+++ b/config/rootfiles/packages/clamav
@@ -48,4 +48,5 @@ var/ipfire/clamav/clamd.conf.sample
var/ipfire/clamav/freshclam.conf
var/ipfire/clamav/freshclam.conf.sample
var/lib/clamav
--usr/local/bin/clamavctrl
+etc/rc.d/init.d/clamav
+usr/local/bin/clamavctrl
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2018-11-04 7:42 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=20181104074252.A17D01081BB0@git01.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