From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. ea6fa0bcef42d3f33fef845c17af8148b6846084
Date: Sat, 06 Mar 2021 16:44:20 +0000 [thread overview]
Message-ID: <4Dt9Rm5M2wz2xdB@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1652 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 ea6fa0bcef42d3f33fef845c17af8148b6846084 (commit)
from 7705df4d5df0fb6cc9261cf946d8113d31718798 (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 ea6fa0bcef42d3f33fef845c17af8148b6846084
Author: Matthias Fischer <matthias.fischer(a)ipfire.org>
Date: Sat Mar 6 15:31:52 2021 +0100
update.sh: Fix path
Signed-off-by: Matthias Fischer <matthias.fischer(a)ipfire.org>
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/core/155/update.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Difference in files:
diff --git a/config/rootfiles/core/155/update.sh b/config/rootfiles/core/155/update.sh
index fd0626588..1434ce666 100644
--- a/config/rootfiles/core/155/update.sh
+++ b/config/rootfiles/core/155/update.sh
@@ -62,7 +62,7 @@ ldconfig
# Disable all connection tracking helper
sed -E -e "s/^CONNTRACK_(.*?)=on/CONNTRACK_\1=off/g" \
- -i /var/ipfire/firewall/optionsfw
+ -i /var/ipfire/optionsfw/settings
# Update Language cache
/usr/local/bin/update-lang-cache
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2021-03-06 16:44 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=4Dt9Rm5M2wz2xdB@people01.haj.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