From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 6f704a3c85dc453e1a8cebafbca5446e59aab6d6
Date: Wed, 06 Feb 2013 20:08:29 +0100 [thread overview]
Message-ID: <20130206190830.73FDF200DC@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2792 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 6f704a3c85dc453e1a8cebafbca5446e59aab6d6 (commit)
from 1d76272bd30ec4933a268be3a6a41c72a43a43f4 (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 6f704a3c85dc453e1a8cebafbca5446e59aab6d6
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Wed Feb 6 20:08:02 2013 +0100
kernel: update to 3.2.38.
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/core/66/update.sh | 6 +++---
lfs/linux | 6 +++---
2 files changed, 6 insertions(+), 6 deletions(-)
Difference in files:
diff --git a/config/rootfiles/core/66/update.sh b/config/rootfiles/core/66/update.sh
index d764c43..e0a7875 100644
--- a/config/rootfiles/core/66/update.sh
+++ b/config/rootfiles/core/66/update.sh
@@ -78,7 +78,7 @@ fi
#
#
-KVER="3.2.37"
+KVER="3.2.38"
MOUNT=`grep "kernel" /boot/grub/grub.conf 2>/dev/null | tail -n 1 `
# Nur den letzten Parameter verwenden
echo $MOUNT > /dev/null
@@ -328,8 +328,8 @@ if [ ! "$(grep "^flags.* pae " /proc/cpuinfo)" == "" ]; then
"core-update-$core: WARNING not enough space for pae kernel."
else
echo "Name: linux-pae" > /opt/pakfire/db/installed/meta-linux-pae
- echo "ProgVersion: 3.2.37" >> /opt/pakfire/db/installed/meta-linux-pae
- echo "Release: 26" >> /opt/pakfire/db/installed/meta-linux-pae
+ echo "ProgVersion: 3.2.38" >> /opt/pakfire/db/installed/meta-linux-pae
+ echo "Release: 27" >> /opt/pakfire/db/installed/meta-linux-pae
fi
fi
diff --git a/lfs/linux b/lfs/linux
index 2bdb9a5..e46a2d4 100644
--- a/lfs/linux
+++ b/lfs/linux
@@ -24,7 +24,7 @@
include Config
-VER = 3.2.37
+VER = 3.2.38
RPI_PATCHES = linux-3.2.27-ada8b44
@@ -35,7 +35,7 @@ DIR_APP = $(DIR_SRC)/$(THISAPP)
CFLAGS =
CXXFLAGS =
-PAK_VER = 27
+PAK_VER = 28
DEPS = ""
VERSUFIX=ipfire$(KCFG)
@@ -71,7 +71,7 @@ objects =$(DL_FILE) \
$(DL_FILE) = $(URL_IPFIRE)/$(DL_FILE)
rpi-patches-$(RPI_PATCHES).patch.xz = $(URL_IPFIRE)/rpi-patches-$(RPI_PATCHES).patch.xz
-$(DL_FILE)_MD5 = 741f0ee132734b8ed887ad1d87cc202b
+$(DL_FILE)_MD5 = 16ea59fd8701f82d7d7c534a6e4bb923
rpi-patches-$(RPI_PATCHES).patch.xz_MD5 = 966687ff27e450e04ff50e0da829dc00
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2013-02-06 19:08 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=20130206190830.73FDF200DC@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