From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 2c1a6768d0117095b74089d96741f60771f70398
Date: Sat, 14 Apr 2018 15:17:21 +0100 [thread overview]
Message-ID: <20180414141721.EE2991081DF2@git01.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2401 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 2c1a6768d0117095b74089d96741f60771f70398 (commit)
from ff2b65c193321fed8c0d92bd5d46366fefcdd9a0 (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 2c1a6768d0117095b74089d96741f60771f70398
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Sat Apr 14 16:14:31 2018 +0200
bump packages
the old packages are linked against removed libs
fixes: 11685
Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
lfs/htop | 2 +-
lfs/iptraf-ng | 2 +-
lfs/lcd4linux | 2 +-
lfs/nano | 2 +-
4 files changed, 4 insertions(+), 4 deletions(-)
Difference in files:
diff --git a/lfs/htop b/lfs/htop
index 6fba6c0bb..fa5d862d7 100644
--- a/lfs/htop
+++ b/lfs/htop
@@ -32,7 +32,7 @@ DL_FROM = $(URL_IPFIRE)
DIR_APP = $(DIR_SRC)/$(THISAPP)
TARGET = $(DIR_INFO)/$(THISAPP)
PROG = htop
-PAK_VER = 10
+PAK_VER = 11
DEPS = ""
diff --git a/lfs/iptraf-ng b/lfs/iptraf-ng
index e962b2c5e..f76ff9f33 100644
--- a/lfs/iptraf-ng
+++ b/lfs/iptraf-ng
@@ -17,7 +17,7 @@ DL_FROM = $(URL_IPFIRE)
DIR_APP = $(DIR_SRC)/$(THISAPP)
TARGET = $(DIR_INFO)/$(THISAPP)
PROG = iptraf-ng
-PAK_VER = 2
+PAK_VER = 3
DEPS = ""
diff --git a/lfs/lcd4linux b/lfs/lcd4linux
index 31bcf12e6..79e9d5a2e 100644
--- a/lfs/lcd4linux
+++ b/lfs/lcd4linux
@@ -32,7 +32,7 @@ DL_FROM = $(URL_IPFIRE)
DIR_APP = $(DIR_SRC)/lcd4linux
TARGET = $(DIR_INFO)/$(THISAPP)
PROG = lcd4linux
-PAK_VER = 5
+PAK_VER = 6
DEPS = "dpfhack libmpdclient"
diff --git a/lfs/nano b/lfs/nano
index 936b4778b..6269ea208 100644
--- a/lfs/nano
+++ b/lfs/nano
@@ -32,7 +32,7 @@ DL_FROM = $(URL_IPFIRE)
DIR_APP = $(DIR_SRC)/$(THISAPP)
TARGET = $(DIR_INFO)/$(THISAPP)
PROG = nano
-PAK_VER = 19
+PAK_VER = 20
DEPS = ""
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2018-04-14 14:17 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=20180414141721.EE2991081DF2@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