From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, core100, updated. 7940649e17a7499fbddb5552793294ee394c7541
Date: Mon, 21 Mar 2016 22:33:17 +0000 [thread overview]
Message-ID: <20160321223317.5B8771081BA6@git01.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1580 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, core100 has been updated
via 7940649e17a7499fbddb5552793294ee394c7541 (commit)
from 33513817fa4eac7007fc4e39c348d7fffdfac20a (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 7940649e17a7499fbddb5552793294ee394c7541
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Mon Mar 21 22:52:03 2016 +0100
core100: update linker config
Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/core/100/update.sh | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
Difference in files:
diff --git a/config/rootfiles/core/100/update.sh b/config/rootfiles/core/100/update.sh
index 9e48d3a..931930a 100644
--- a/config/rootfiles/core/100/update.sh
+++ b/config/rootfiles/core/100/update.sh
@@ -139,7 +139,8 @@ esac
# Extract files
tar xavf /opt/pakfire/tmp/files* --no-overwrite-dir -p --numeric-owner -C /
-
+# update linker config
+ldconfig
# Check diskspace on boot
BOOTSPACE=`df /boot -Pk | sed "s| * | |g" | cut -d" " -f4 | tail -n 1`
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2016-03-21 22:33 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=20160321223317.5B8771081BA6@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