From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. bf5e1c4c52828c48d6c51b6830f9d696be261877
Date: Tue, 14 Jan 2014 17:53:59 +0100 [thread overview]
Message-ID: <20140114165359.94FF321E4C@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1756 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 bf5e1c4c52828c48d6c51b6830f9d696be261877 (commit)
from dd62fd25cde358524861fdd8e20aed1a83c6a6da (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 bf5e1c4c52828c48d6c51b6830f9d696be261877
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Tue Jan 14 17:53:14 2014 +0100
fifteen: increase size of pae kernel.
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/core/76/update.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Difference in files:
diff --git a/config/rootfiles/core/76/update.sh b/config/rootfiles/core/76/update.sh
index c572e7c..eafb3cf 100644
--- a/config/rootfiles/core/76/update.sh
+++ b/config/rootfiles/core/76/update.sh
@@ -341,7 +341,7 @@ rm -rf /opt/pakfire/db/*/meta-linux-pae
if [ ! "$(grep "^flags.* pae " /proc/cpuinfo)" == "" ]; then
ROOTSPACE=`df / -Pk | sed "s| * | |g" | cut -d" " -f4 | tail -n 1`
BOOTSPACE=`df /boot -Pk | sed "s| * | |g" | cut -d" " -f4 | tail -n 1`
- if [ $BOOTSPACE -lt 9000 -o $ROOTSPACE -lt 90000 ]; then
+ if [ $BOOTSPACE -lt 12000 -o $ROOTSPACE -lt 90000 ]; then
/usr/bin/logger -p syslog.emerg -t ipfire \
"core-update-$core: WARNING not enough space for pae kernel."
else
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2014-01-14 16:53 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=20140114165359.94FF321E4C@argus.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