public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] Tor: update to 0.4.1.6
Date: Wed, 25 Sep 2019 16:18:50 +0100	[thread overview]
Message-ID: <4B47CA32-38AA-4F98-85B6-F67A140C1B51@ipfire.org> (raw)
In-Reply-To: <c47c9e8e-5c6d-964b-9cd1-ef077f8c31c2@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 1407 bytes --]

Hi,

> On 25 Sep 2019, at 16:15, peter.mueller(a)ipfire.org wrote:
> 
> Please refer to https://blog.torproject.org/new-release-tor-0416 for
> release notes. This patch has to be applied after applying 9fb607ef6
> (https://patchwork.ipfire.org/patch/2407/), which was not merged at
> the time of writing.

Referring to the commit by its hash does not make any sense here, because it will change if the patch is being merged into master.

Just FYI.

Reviewed-by: Michael Tremer <michael.tremer(a)ipfire.org>

> 
> Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org>
> ---
> lfs/tor | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/lfs/tor b/lfs/tor
> index 9fb607ef6..ea07f6ce2 100644
> --- a/lfs/tor
> +++ b/lfs/tor
> @@ -24,7 +24,7 @@
> 
> include Config
> 
> -VER        = 0.4.1.5
> +VER        = 0.4.1.6
> 
> THISAPP    = tor-$(VER)
> DL_FILE    = $(THISAPP).tar.gz
> @@ -32,7 +32,7 @@ DL_FROM    = $(URL_IPFIRE)
> DIR_APP    = $(DIR_SRC)/$(THISAPP)
> TARGET     = $(DIR_INFO)/$(THISAPP)
> PROG       = tor
> -PAK_VER    = 42
> +PAK_VER    = 43
> 
> DEPS       = "libseccomp"
> 
> @@ -44,7 +44,7 @@ objects = $(DL_FILE)
> 
> $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
> 
> -$(DL_FILE)_MD5 = 4a7ee49500d536d6c301a73bac0d0393
> +$(DL_FILE)_MD5 = d5e290d2a09d4225693cebc37a83097f
> 
> install : $(TARGET)
> 
> -- 
> 2.16.4


      reply	other threads:[~2019-09-25 15:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-25 15:15 peter.mueller
2019-09-25 15:18 ` Michael Tremer [this message]

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=4B47CA32-38AA-4F98-85B6-F67A140C1B51@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=development@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