From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. bfdab6e3644fef33b22dfcf10e641ebdf8b55367
Date: Thu, 10 Jul 2014 17:14:47 +0200 [thread overview]
Message-ID: <20140710151447.AC4CD2139A@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1685 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 bfdab6e3644fef33b22dfcf10e641ebdf8b55367 (commit)
from f0b7534f7f7b853f993bcb9e5b3f717167df416e (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 bfdab6e3644fef33b22dfcf10e641ebdf8b55367
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Thu Jul 10 17:12:59 2014 +0200
transmission: security update to 2.84.
-----------------------------------------------------------------------
Summary of changes:
lfs/transmission | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
Difference in files:
diff --git a/lfs/transmission b/lfs/transmission
index cb4ad45..3a1cbdd 100644
--- a/lfs/transmission
+++ b/lfs/transmission
@@ -24,7 +24,7 @@
include Config
-VER = 2.83
+VER = 2.84
THISAPP = transmission-$(VER)
DL_FILE = $(THISAPP).tar.xz
@@ -32,7 +32,7 @@ DL_FROM = $(URL_IPFIRE)
DIR_APP = $(DIR_SRC)/$(THISAPP)
TARGET = $(DIR_INFO)/$(THISAPP)
PROG = transmission
-PAK_VER = 10
+PAK_VER = 11
DEPS = "libevent2"
@@ -46,7 +46,7 @@ objects = $(DL_FILE)
$(DL_FILE) = $(DL_FROM)/$(DL_FILE)
-$(DL_FILE)_MD5 = 4620cfbfefee2ce55a6fa12c3ec330a7
+$(DL_FILE)_MD5 = 411aec1c418c14f6765710d89743ae42
install : $(TARGET)
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2014-07-10 15: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=20140710151447.AC4CD2139A@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