public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: [PATCH v2] Tor: update to 0.4.4.6
Date: Sun, 22 Nov 2020 12:20:48 +0000	[thread overview]
Message-ID: <c7749c9d-096d-4224-c050-5efd2cec39b0@ipfire.org> (raw)
In-Reply-To: <FD7DDE78-BEC7-42BD-9749-6BBA060549A6@ipfire.org>

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

Full changelog can be obtained from https://gitweb.torproject.org/tor.git/plain/ChangeLog?h=tor-0.4.4.6 .

The second version of this patch should apply correctly against "next", but I have no idea
why it did not do so in the first place. :-/

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 b7c28495d..6d758dcb0 100644
--- a/lfs/tor
+++ b/lfs/tor
@@ -24,7 +24,7 @@
  
  include Config
  
-VER        = 0.4.4.5
+VER        = 0.4.4.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    = 55
+PAK_VER    = 56
  
  DEPS       = libseccomp
  
@@ -44,7 +44,7 @@ objects = $(DL_FILE)
  
  $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
  
-$(DL_FILE)_MD5 = b061b7c4ce6102fb7c800b73c8573388
+$(DL_FILE)_MD5 = 3635b2f7b6645910bf702ce8eaeffd0d
  
  install : $(TARGET)
  
-- 
2.20.1


  reply	other threads:[~2020-11-22 12:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-20 16:53 [PATCH] " Peter Müller
2020-11-20 20:01 ` Michael Tremer
2020-11-22 12:20   ` Peter Müller [this message]
2020-11-23 11:25     ` [PATCH v2] " Michael Tremer

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=c7749c9d-096d-4224-c050-5efd2cec39b0@ipfire.org \
    --to=peter.mueller@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