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, next, updated. d14229c0da139a3dca3bff3b95a6dafdc7a52f93
Date: Sat, 05 Jan 2013 15:14:26 +0100	[thread overview]
Message-ID: <20130105141426.87D0E2010D@argus.ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 2307 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  d14229c0da139a3dca3bff3b95a6dafdc7a52f93 (commit)
      from  7234a472adac6d5e8111c529570fe4cfe873fac0 (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 d14229c0da139a3dca3bff3b95a6dafdc7a52f93
Author: Arne Fitzenreiter <Arne_F(a)ipfire.org>
Date:   Sat Jan 5 15:13:55 2013 +0100

    kernel: bump package version.

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

Summary of changes:
 config/rootfiles/core/66/update.sh | 4 ++--
 lfs/linux                          | 2 +-
 2 files changed, 3 insertions(+), 3 deletions(-)

Difference in files:
diff --git a/config/rootfiles/core/66/update.sh b/config/rootfiles/core/66/update.sh
index cf40844..750f8aa 100644
--- a/config/rootfiles/core/66/update.sh
+++ b/config/rootfiles/core/66/update.sh
@@ -114,7 +114,7 @@ add_to_backup usr/local/bin/vpn-watch
 add_to_backup usr/libexec/ipsec
 
 # Backup the files
-tar cJvf /var/ipfire/backup/core-upgrade_$KVER.tar.xz \
+tar cJvf /var/ipfire/backup/core-upgrade$core_$KVER.tar.xz \
     -C / -T /opt/pakfire/tmp/ROOTFILES --exclude='#*' --exclude='/var/cache' > /dev/null 2>&1
 
 # Check diskspace on root
@@ -321,7 +321,7 @@ if [ ! "$(grep "^flags.* pae " /proc/cpuinfo)" == "" ]; then
 	else
 		echo "Name: linux-pae" > /opt/pakfire/db/installed/meta-linux-pae
 		echo "ProgVersion: 3.2.35" >> /opt/pakfire/db/installed/meta-linux-pae
-		echo "Release: 24"     >> /opt/pakfire/db/installed/meta-linux-pae
+		echo "Release: 25"     >> /opt/pakfire/db/installed/meta-linux-pae
 	fi
 fi
 
diff --git a/lfs/linux b/lfs/linux
index f8cd7d5..e85f21a 100644
--- a/lfs/linux
+++ b/lfs/linux
@@ -35,7 +35,7 @@ DIR_APP    = $(DIR_SRC)/$(THISAPP)
 CFLAGS     =
 CXXFLAGS   =
 
-PAK_VER    = 25
+PAK_VER    = 26
 DEPS	   = ""
 
 VERSUFIX=ipfire$(KCFG)


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

                 reply	other threads:[~2013-01-05 14:14 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=20130105141426.87D0E2010D@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