public inbox for ipfire-scm@lists.ipfire.org
 help / color / mirror / Atom feed
From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, thirteen, updated. 83601a06bc8036b21e9b6c6911c8096e35bd443d
Date: Sun, 25 Nov 2012 13:10:34 +0100	[thread overview]
Message-ID: <20121125121034.B2955202F6@argus.ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 2881 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, thirteen has been updated
       via  83601a06bc8036b21e9b6c6911c8096e35bd443d (commit)
      from  0eb9a71a7b5dfce4425b9ca6e1e9dfb47dac6dac (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 83601a06bc8036b21e9b6c6911c8096e35bd443d
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date:   Sun Nov 25 13:09:34 2012 +0100

    kernel: bump package release.

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

Summary of changes:
 config/rootfiles/core/66/update.sh | 8 ++++----
 lfs/linux                          | 2 +-
 lfs/linux2                         | 2 +-
 3 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 144d48c..815ff7d 100644
--- a/config/rootfiles/core/66/update.sh
+++ b/config/rootfiles/core/66/update.sh
@@ -239,15 +239,15 @@ rm -rf /opt/pakfire/db/*/meta-glib
 rm -rf /opt/pakfire/db/*/meta-linux-pae
 if [ ! "$(grep "^flags.* pae " /proc/cpuinfo)" == "" ]; then
 	echo "Name: linux-pae" > /opt/pakfire/db/installed/meta-linux-pae
-	echo "ProgVersion: 0" >> /opt/pakfire/db/installed/meta-linux-pae
-	echo "Release: 0"     >> /opt/pakfire/db/installed/meta-linux-pae
+	echo "ProgVersion: 3.2.34" >> /opt/pakfire/db/installed/meta-linux-pae
+	echo "Release: 23"     >> /opt/pakfire/db/installed/meta-linux-pae
 fi
 
 # Force reinstall xen kernel if it was installed
 if [ -e "/opt/pakfire/db/installed/meta-linux-xen" ]; then
 	echo "Name: linux-xen" > /opt/pakfire/db/installed/meta-linux-xen
-	echo "ProgVersion: 0" >> /opt/pakfire/db/installed/meta-linux-xen
-	echo "Release: 0"     >> /opt/pakfire/db/installed/meta-linux-xen
+	echo "ProgVersion: 2.6.32.60" >> /opt/pakfire/db/installed/meta-linux-xen
+	echo "Release: 23"     >> /opt/pakfire/db/installed/meta-linux-xen
 fi
 
 #
diff --git a/lfs/linux b/lfs/linux
index 1c5448c..d6c9555 100644
--- a/lfs/linux
+++ b/lfs/linux
@@ -35,7 +35,7 @@ DIR_APP    = $(DIR_SRC)/$(THISAPP)
 CFLAGS     =
 CXXFLAGS   =
 
-PAK_VER    = 23
+PAK_VER    = 24
 DEPS	   = ""
 
 VERSUFIX=ipfire$(KCFG)
diff --git a/lfs/linux2 b/lfs/linux2
index c3ac3ee..4504035 100644
--- a/lfs/linux2
+++ b/lfs/linux2
@@ -34,7 +34,7 @@ DIR_APP    = $(DIR_SRC)/$(THISAPP)
 CFLAGS     =
 CXXFLAGS   =
 
-PAK_VER    = 21
+PAK_VER    = 24
 DEPS	   = ""
 
 # Normal build or XEN build.


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

                 reply	other threads:[~2012-11-25 12:10 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=20121125121034.B2955202F6@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