From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. a30c851f2f5e94680d983576bb13cc2f0e27ebc2
Date: Mon, 27 Jul 2026 15:41:16 +0000 (UTC) [thread overview]
Message-ID: <4h82rD6HjJz2xgJ@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 a30c851f2f5e94680d983576bb13cc2f0e27ebc2 (commit)
from 65574466679195a8cf114660b2665284ebe1089d (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 a30c851f2f5e94680d983576bb13cc2f0e27ebc2
Author: Michael Tremer <michael.tremer@ipfire.org>
Date: Mon Jul 27 15:41:05 2026 +0000
core205: Remove unboundctrl
Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/core/205/update.sh | 2 ++
1 file changed, 2 insertions(+)
Difference in files:
diff --git a/config/rootfiles/core/205/update.sh b/config/rootfiles/core/205/update.sh
index aae3c39c1..25443bf90 100644
--- a/config/rootfiles/core/205/update.sh
+++ b/config/rootfiles/core/205/update.sh
@@ -34,6 +34,8 @@ done
# Stop services
# Remove files
+rm -rfv \
+ /usr/local/bin/unboundctrl
# Extract files
extract_files
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2026-07-27 15:41 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=4h82rD6HjJz2xgJ@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