From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 091050ab1610a60a7bd0c00bc35dd09faf925e4c
Date: Thu, 28 May 2026 14:13:35 +0000 (UTC) [thread overview]
Message-ID: <4gR7kl1ZBqz2xMt@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 091050ab1610a60a7bd0c00bc35dd09faf925e4c (commit)
from 041cd0f9bb3b0801eef390354d7470d16d2f667e (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 091050ab1610a60a7bd0c00bc35dd09faf925e4c
Author: Michael Tremer <michael.tremer@ipfire.org>
Date: Thu May 28 16:13:12 2026 +0200
knot resolver: Fix ownership of leases.db
Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
lfs/knot-resolver | 1 +
1 file changed, 1 insertion(+)
Difference in files:
diff --git a/lfs/knot-resolver b/lfs/knot-resolver
index 3d7d65c74..6bcfd6820 100644
--- a/lfs/knot-resolver
+++ b/lfs/knot-resolver
@@ -109,6 +109,7 @@ $(TARGET) : $(patsubst %,$(DIR_DL)/%,$(objects))
# Create the leases database
sqlite3 "/var/lib/knot-resolver/leases.db" \
< /usr/lib/knot-resolver/leases.schema
+ chown knot-resolver:knot-resolver /var/lib/knot-resolver/leases.db
# Install the DHCP leases helper script
install -v -m 755 $(DIR_SRC)/config/knot-resolver/dhcp-lease \
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2026-05-28 14:13 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=4gR7kl1ZBqz2xMt@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