From: Arne Fitzenreiter <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, core129, updated. 67173e2831d55bf548ce6639a58d86f526761842
Date: Thu, 14 Mar 2019 09:55:26 +0000 [thread overview]
Message-ID: <20190314095527.867BF84FDD4@people01.i.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1793 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, core129 has been updated
via 67173e2831d55bf548ce6639a58d86f526761842 (commit)
from 4fc1a0045b48b1a459256d146030279c9905a13e (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 67173e2831d55bf548ce6639a58d86f526761842
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Thu Mar 14 10:54:22 2019 +0100
core129: remove old dracut files and rebuilt the initrd
Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/core/129/update.sh | 8 ++++++--
1 file changed, 6 insertions(+), 2 deletions(-)
Difference in files:
diff --git a/config/rootfiles/core/129/update.sh b/config/rootfiles/core/129/update.sh
index 62a278ce5..dfeeeaa1e 100644
--- a/config/rootfiles/core/129/update.sh
+++ b/config/rootfiles/core/129/update.sh
@@ -40,7 +40,8 @@ done
# Remove files
rm -vf \
- /usr/lib/firewall/ipsec-block
+ /usr/lib/firewall/ipsec-block \
+ /sbin/dracut*
# Extract files
extract_files
@@ -59,8 +60,11 @@ ldconfig
/usr/local/bin/openvpnctrl -sn2n
/etc/init.d/squid start
+# Rebuild initrd
+rebuild-initrd
+
# This update needs a reboot...
-#touch /var/run/need_reboot
+touch /var/run/need_reboot
# Finish
/etc/init.d/fireinfo start
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2019-03-14 9:55 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=20190314095527.867BF84FDD4@people01.i.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