From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 5f1fb754f54c5bee40186a69763ec9e0b3a308a0
Date: Fri, 22 May 2026 09:36:32 +0000 (UTC) [thread overview]
Message-ID: <4gMKsr1lHTz2xKn@people01.haj.ipfire.org> (raw)
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 5f1fb754f54c5bee40186a69763ec9e0b3a308a0 (commit)
from ebe438926d76400a83ee822ef5911b2a7c69c03e (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 5f1fb754f54c5bee40186a69763ec9e0b3a308a0
Author: Michael Tremer <michael.tremer@ipfire.org>
Date: Fri May 22 09:33:49 2026 +0000
knot-resolver: Install our configuration file
Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
lfs/knot-resolver | 4 ++++
1 file changed, 4 insertions(+)
Difference in files:
diff --git a/lfs/knot-resolver b/lfs/knot-resolver
index 3073555c7..27b613de3 100644
--- a/lfs/knot-resolver
+++ b/lfs/knot-resolver
@@ -90,6 +90,10 @@ $(TARGET) : $(patsubst %,$(DIR_DL)/%,$(objects))
cd $(DIR_APP) && ninja -C builddir/ install
cd $(DIR_APP) && python3 setup.py install --root=/
+ # Install our configuration file
+ install -v -m 644 $(DIR_SRC)/config/knot-resolver/config.yaml \
+ /etc/knot-resolver/config.yaml
+
# Install our configuration helper script
install -v -m 644 $(DIR_SRC)/config/knot-resolver/config.lua \
/usr/lib/knot-resolver/config.lua
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2026-05-22 9:36 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=4gMKsr1lHTz2xKn@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