From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 49c7a4b8284bbf03019f7b1565ac7d55ba2eacec
Date: Sun, 07 Apr 2013 10:06:35 +0200 [thread overview]
Message-ID: <20130407080645.1A48720131@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1673 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 49c7a4b8284bbf03019f7b1565ac7d55ba2eacec (commit)
from 7e4a0896637b38cb37c3bdca6984f397fc9b16a7 (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 49c7a4b8284bbf03019f7b1565ac7d55ba2eacec
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Sun Apr 7 10:06:15 2013 +0200
transmission: update to 2.77.
-----------------------------------------------------------------------
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 ab34ee3..083db58 100644
--- a/lfs/transmission
+++ b/lfs/transmission
@@ -24,7 +24,7 @@
include Config
-VER = 2.76
+VER = 2.77
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 = 5
+PAK_VER = 6
DEPS = "libevent2"
@@ -44,7 +44,7 @@ objects = $(DL_FILE)
$(DL_FILE) = $(DL_FROM)/$(DL_FILE)
-$(DL_FILE)_MD5 = 9abbffe29ce9b5ee68a116d293c51111
+$(DL_FILE)_MD5 = 60c0e77a1852656215f7102a437b2a3d
install : $(TARGET)
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2013-04-07 8:06 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=20130407080645.1A48720131@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