public inbox for ipfire-scm@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. af92e2e3d6a4ddc818a6d35dc36baa26621b6cb3
Date: Tue, 02 Jun 2026 14:24:00 +0000 (UTC)	[thread overview]
Message-ID: <4gVCkS6Hbzz2xHq@people01.haj.ipfire.org> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2720 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  af92e2e3d6a4ddc818a6d35dc36baa26621b6cb3 (commit)
       via  aaf75c0d1a7999ffdd181897d37d168ce2092214 (commit)
       via  7aaf6dc422377e56d2594c2c37787ca715343d38 (commit)
      from  bc12c6119d3ef4050b2efc66f49cdcaec052079f (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 af92e2e3d6a4ddc818a6d35dc36baa26621b6cb3
Author: Daniel Weismüller <daniel.weismueller@ipfire.org>
Date:   Tue Jun 2 16:23:07 2026 +0200

    core203: Update the RPZs in background after the updater
    
    Signed-off-by: Daniel Weismüller <daniel.weismueller@ipfire.org>

commit aaf75c0d1a7999ffdd181897d37d168ce2092214
Author: Daniel Weismüller <daniel.weismueller@ipfire.org>
Date:   Tue Jun 2 16:19:00 2026 +0200

    core203: Only try to stop Unbound if it is still there
    
    Signed-off-by: Daniel Weismüller <daniel.weismueller@ipfire.org>

commit 7aaf6dc422377e56d2594c2c37787ca715343d38
Author: Daniel Weismüller <daniel.weismueller@ipfire.org>
Date:   Tue Jun 2 16:17:50 2026 +0200

    core203: Create leases.db if it does not exist
    
    Signed-off-by: Daniel Weismüller <daniel.weismueller@ipfire.org>

-----------------------------------------------------------------------

Summary of changes:
 config/rootfiles/core/203/update.sh | 16 ++++++++++++++--
 1 file changed, 14 insertions(+), 2 deletions(-)

Difference in files:
diff --git a/config/rootfiles/core/203/update.sh b/config/rootfiles/core/203/update.sh
index 0b1bcfa66..5aea2ff66 100644
--- a/config/rootfiles/core/203/update.sh
+++ b/config/rootfiles/core/203/update.sh
@@ -74,9 +74,18 @@ fi
 # Extract files
 extract_files
 
+# Create leases.db if it does not exist, yet
+if [ -e "/var/lib/knot-resolver/leases.db" ]; then
+	sqlite3 "/var/lib/knot-resolver/leases.db" \
+		< /usr/lib/knot-resolver/leases.schema
+	chown knot-resolver:knot-resolver /var/lib/knot-resolver/leases.db
+fi
+
 # Stop Unbound & start Knot Resolver
-/etc/init.d/unbound stop
-/etc/init.d/knot-resolver start
+if [ -x "/etc/init.d/unbound" ]; then
+	/etc/init.d/unbound stop
+	/etc/init.d/knot-resolver start
+fi
 
 # Remove Unbound
 rm -rfv \
@@ -112,6 +121,9 @@ ldconfig
 
 # Start services
 
+# Re-fetch any RPZs in background
+/usr/local/bin/update-rpzs &
+
 # Reload crontab
 fcrontab -z
 


hooks/post-receive
--
IPFire 2.x development tree


                 reply	other threads:[~2026-06-02 14:24 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=4gVCkS6Hbzz2xHq@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