From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 33a2aff4168db7554ce26b574443bcb2dc58434d
Date: Fri, 16 Aug 2024 10:00:40 +0000 [thread overview]
Message-ID: <4Wlctw1NpNz2xWt@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1492 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 33a2aff4168db7554ce26b574443bcb2dc58434d (commit)
from d388d0c1039cd52953e146fac3eae85c411ac7b8 (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 33a2aff4168db7554ce26b574443bcb2dc58434d
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Fri Aug 16 10:00:29 2024 +0000
core188: Ship unbound
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/core/188/update.sh | 1 +
1 file changed, 1 insertion(+)
Difference in files:
diff --git a/config/rootfiles/core/188/update.sh b/config/rootfiles/core/188/update.sh
index 704450f89..185ca16cf 100644
--- a/config/rootfiles/core/188/update.sh
+++ b/config/rootfiles/core/188/update.sh
@@ -67,6 +67,7 @@ ldconfig
# Start services
/etc/init.d/apache restart
+/etc/init.d/unbound restart
# Build initial ramdisks (for intel-microcode)
dracut --regenerate-all --force
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2024-08-16 10:00 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=4Wlctw1NpNz2xWt@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