public inbox for ipfire-scm@lists.ipfire.org
 help / color / mirror / Atom feed
From: Arne Fitzenreiter <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. a0f37487475e510f12b5ced95b897af05598c7c5
Date: Fri, 09 Nov 2018 20:13:30 +0000	[thread overview]
Message-ID: <20181109201330.ADA1F1081BB0@git01.ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 2500 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  a0f37487475e510f12b5ced95b897af05598c7c5 (commit)
       via  f52ef2ce5a75bd54a574232748bb71d0f866ba4e (commit)
      from  db6b40500c269d83bd2e84cb89c5414712cde394 (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 a0f37487475e510f12b5ced95b897af05598c7c5
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date:   Fri Nov 9 21:12:02 2018 +0100

    core125: finish update
    
    Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>

commit f52ef2ce5a75bd54a574232748bb71d0f866ba4e
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date:   Fri Nov 9 21:09:06 2018 +0100

    core125: restart init after glibc uodate
    
    without restart remount of / will fail and may result in
    a filesystem corruption at next boot.
    
    Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>

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

Summary of changes:
 config/rootfiles/core/125/update.sh | 3 +++
 make.sh                             | 2 +-
 2 files changed, 4 insertions(+), 1 deletion(-)

Difference in files:
diff --git a/config/rootfiles/core/125/update.sh b/config/rootfiles/core/125/update.sh
index a4ae0993c..62214339e 100644
--- a/config/rootfiles/core/125/update.sh
+++ b/config/rootfiles/core/125/update.sh
@@ -40,6 +40,9 @@ extract_files
 # update linker config
 ldconfig
 
+# restart init after glibc uodate
+telinit u
+
 # Update Language cache
 /usr/local/bin/update-lang-cache
 
diff --git a/make.sh b/make.sh
index 73f8d61ec..7e6975299 100755
--- a/make.sh
+++ b/make.sh
@@ -26,7 +26,7 @@ NAME="IPFire"							# Software name
 SNAME="ipfire"							# Short name
 VERSION="2.21"							# Version number
 CORE="125"							# Core Level (Filename)
-PAKFIRE_CORE="124"						# Core Level (PAKFIRE)
+PAKFIRE_CORE="125"						# Core Level (PAKFIRE)
 GIT_BRANCH=`git rev-parse --abbrev-ref HEAD`			# Git Branch
 SLOGAN="www.ipfire.org"						# Software slogan
 CONFIG_ROOT=/var/ipfire						# Configuration rootdir


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

                 reply	other threads:[~2018-11-09 20:13 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=20181109201330.ADA1F1081BB0@git01.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