From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 48679b583edc32f7d7a81f7e1b52c7b0a2a1175e
Date: Tue, 27 Oct 2026 11:28:38 +0000 (UTC) [thread overview]
Message-ID: <4jDStG463Tz2xRB@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 48679b583edc32f7d7a81f7e1b52c7b0a2a1175e (commit)
via f4c574a71e475dab09b31d83efa9cba03a5ac30b (commit)
from 0a32e2f01a0942dcd5a3012a4f9ecf9c0edcd30d (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 48679b583edc32f7d7a81f7e1b52c7b0a2a1175e
Author: Michael Tremer <michael.tremer@ipfire.org>
Date: Tue Oct 27 11:28:36 2026 +0000
core206: Ship the pakfire initscript
Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
commit f4c574a71e475dab09b31d83efa9cba03a5ac30b
Author: Michael Tremer <michael.tremer@ipfire.org>
Date: Tue Oct 27 11:28:31 2026 +0000
core206: Ship pakfire
Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/core/206/filelists/files | 3 +++
config/rootfiles/{oldcore/167 => core/206}/filelists/pakfire | 0
2 files changed, 3 insertions(+)
copy config/rootfiles/{oldcore/167 => core/206}/filelists/pakfire (100%)
Difference in files:
diff --git a/config/rootfiles/core/206/filelists/files b/config/rootfiles/core/206/filelists/files
index 123e7bf38..28d9291d7 100644
--- a/config/rootfiles/core/206/filelists/files
+++ b/config/rootfiles/core/206/filelists/files
@@ -2,14 +2,17 @@ etc/httpd/conf/vhosts.d/ipfire-interface-ssl.conf
etc/rc.d/init.d/firewall
etc/rc.d/init.d/networking/red
etc/rc.d/init.d/openvpn-n2n
+etc/rc.d/init.d/pakfire
etc/rc.d/init.d/rrd
etc/rc.d/init.d/sensors
etc/rc.d/init.d/telemetryd
+etc/rc.d/rc0.d/K00pakfire
etc/rc.d/rc0.d/K81rrd
etc/rc.d/rc0.d/K84telemetryd
etc/rc.d/rc3.d/S15sensors
etc/rc.d/rc3.d/S16telemetryd
etc/rc.d/rc3.d/S19rrd
+etc/rc.d/rc6.d/K00pakfire
etc/rc.d/rc6.d/K81rrd
etc/rc.d/rc6.d/K84telemetryd
etc/strongswan.d/charon.conf
diff --git a/config/rootfiles/core/206/filelists/pakfire b/config/rootfiles/core/206/filelists/pakfire
new file mode 120000
index 000000000..d5b1d0d03
--- /dev/null
+++ b/config/rootfiles/core/206/filelists/pakfire
@@ -0,0 +1 @@
+../../../common/pakfire
\ No newline at end of file
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2026-10-27 11:28 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=4jDStG463Tz2xRB@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