From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, fifteen, updated. 78403883e23271c9a7ab2bdfeeaf64cc20fd11b4
Date: Wed, 02 Oct 2013 22:43:37 +0200 [thread overview]
Message-ID: <20131002204338.08C8220F76@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1747 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, fifteen has been updated
via 78403883e23271c9a7ab2bdfeeaf64cc20fd11b4 (commit)
from 5b6acb88c607b2b9a46365281e611706c0c12109 (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 78403883e23271c9a7ab2bdfeeaf64cc20fd11b4
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Wed Oct 2 22:43:07 2013 +0200
vdr: update to 2.0.3.
-----------------------------------------------------------------------
Summary of changes:
lfs/vdr | 10 +++++++---
1 file changed, 7 insertions(+), 3 deletions(-)
Difference in files:
diff --git a/lfs/vdr b/lfs/vdr
index b1feb01..161b04e 100644
--- a/lfs/vdr
+++ b/lfs/vdr
@@ -24,8 +24,12 @@
include Config
-VER = 2.0.1
+VER = 2.0.3
+
+# VDRPLUGVER must match with APIVERSION in config.h
+# after change this update also all vdr plugins
VDRPLUGVER = 2.0.0
+
THISAPP = vdr-$(VER)
DL_FILE = $(THISAPP).tar.bz2
@@ -33,7 +37,7 @@ DL_FROM = $(URL_IPFIRE)
DIR_APP = $(DIR_SRC)/$(THISAPP)
TARGET = $(DIR_INFO)/$(THISAPP)
PROG = vdr
-PAK_VER = 7
+PAK_VER = 8
DEPS = "vdr_streamdev"
@@ -61,7 +65,7 @@ objects = $(DL_FILE)
$(DL_FILE) = $(DL_FROM)/$(DL_FILE)
-$(DL_FILE)_MD5 = e1b7a76c57c96300829dccd39eb20e7d
+$(DL_FILE)_MD5 = dd8fb1642bdfa7feb0e9a8ae41e9ef2f
install : $(TARGET)
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2013-10-02 20:43 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=20131002204338.08C8220F76@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