From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, core122, updated. 5c61912dc39ab7357f0821d9a357e8505581e48d
Date: Mon, 30 Jul 2018 21:58:24 +0100 [thread overview]
Message-ID: <20180730205824.E23071081BD5@git01.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1657 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, core122 has been updated
via 5c61912dc39ab7357f0821d9a357e8505581e48d (commit)
from c645bac12b753d9b8d95d61cff9b828ccbe3d391 (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 5c61912dc39ab7357f0821d9a357e8505581e48d
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Mon Jul 30 22:22:31 2018 +0200
core121: lower needed disksapce on /boot
the old value will sometimes fail on pae systems.
Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/core/121/update.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Difference in files:
diff --git a/config/rootfiles/core/121/update.sh b/config/rootfiles/core/121/update.sh
index bee8fd24f..ca64b643d 100644
--- a/config/rootfiles/core/121/update.sh
+++ b/config/rootfiles/core/121/update.sh
@@ -61,7 +61,7 @@ fi
BOOTSPACE=`df /boot -Pk | sed "s| * | |g" | cut -d" " -f4 | tail -n 1`
-if [ $BOOTSPACE -lt 22000 ]; then
+if [ $BOOTSPACE -lt 19000 ]; then
exit_with_error "ERROR cannot update because not enough free space on /boot." 3
exit 3
fi
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2018-07-30 20:58 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=20180730205824.E23071081BD5@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